Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b79905e9665b775cef86ee5de7b769532c924e635c4ef566980b0b5d84e5f06c

Tx prefix hash: e3d2cd18c080408a1b2a5d0c99be3a7d882c857b97546577e18b2596d44fa665
Tx public key: 7a678cbaafb492cd908828d5e642b06caf9c82c660c293bd32e4da72c88b1533
Timestamp: 1711291391 Timestamp [UCT]: 2024-03-24 14:43:11 Age [y:d:h:m:s]: 00:306:08:50:48
Block: 985374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219235 RingCT/type: yes/0
Extra: 017a678cbaafb492cd908828d5e642b06caf9c82c660c293bd32e4da72c88b153302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f7d48d67ed063346b1b63172d0bdf42c85c0d22a81bf5e6ece33a12a0641b10 0.600000000000 1445583 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 985384, "vin": [ { "gen": { "height": 985374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7d48d67ed063346b1b63172d0bdf42c85c0d22a81bf5e6ece33a12a0641b10" } } ], "extra": [ 1, 122, 103, 140, 186, 175, 180, 146, 205, 144, 136, 40, 213, 230, 66, 176, 108, 175, 156, 130, 198, 96, 194, 147, 189, 50, 228, 218, 114, 200, 139, 21, 51, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8