Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e709d278cb4ff254196810a607324346e9ab12369ea2996f8d8eae17a560801

Tx prefix hash: 0cc4bd180760a42c7d56c59a3f6a16e852a012eae2932a97f9f37ec3da893fd1
Tx public key: dfdf9713481383621742bb90cbfa2a60ac2ef0f62a2bf98fd9236ec0614d7986
Timestamp: 1713894061 Timestamp [UCT]: 2024-04-23 17:41:01 Age [y:d:h:m:s]: 00:201:12:40:23
Block: 1006926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144270 RingCT/type: yes/0
Extra: 01dfdf9713481383621742bb90cbfa2a60ac2ef0f62a2bf98fd9236ec0614d79860211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09519ea84eb4e4d2c2bd49736a72ba98aea5c3f8a1335cfe54a1cacd14ff4b84 0.600000000000 1468116 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": 1006936, "vin": [ { "gen": { "height": 1006926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09519ea84eb4e4d2c2bd49736a72ba98aea5c3f8a1335cfe54a1cacd14ff4b84" } } ], "extra": [ 1, 223, 223, 151, 19, 72, 19, 131, 98, 23, 66, 187, 144, 203, 250, 42, 96, 172, 46, 240, 246, 42, 43, 249, 143, 217, 35, 110, 192, 97, 77, 121, 134, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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