Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e986fceb1d81a1d54a2c1ca66567c2bfbb306fa63b585177e407f056683e4047

Tx prefix hash: 373aae94991a697059803163aa766a91d19473f69559b4f2aa32b74708e9d541
Tx public key: f9495c486244d4fdd699a351f828b8f9f935580f5c093c0b2c696143d3cc55ae
Timestamp: 1712436965 Timestamp [UCT]: 2024-04-06 20:56:05 Age [y:d:h:m:s]: 00:358:22:22:58
Block: 994828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256637 RingCT/type: yes/0
Extra: 01f9495c486244d4fdd699a351f828b8f9f935580f5c093c0b2c696143d3cc55ae02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 802cfdf0a9e60a7f6ea7fe7387950817a7ea899c149edc111cee8107ed88710d 0.600000000000 1455232 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": 994838, "vin": [ { "gen": { "height": 994828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "802cfdf0a9e60a7f6ea7fe7387950817a7ea899c149edc111cee8107ed88710d" } } ], "extra": [ 1, 249, 73, 92, 72, 98, 68, 212, 253, 214, 153, 163, 81, 248, 40, 184, 249, 249, 53, 88, 15, 92, 9, 60, 11, 44, 105, 97, 67, 211, 204, 85, 174, 2, 17, 0, 0, 0, 2, 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