Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e86e9d78b05363ce46ca9b74bd16151991b355e851a5be41fa9c8225df2335

Tx prefix hash: bcfe1c663f0791a75bd1dc50e4c711c163d58b033fe52e88c35d0fa8002a1ea6
Tx public key: b016c95d982366316d8e109fdde8739a85fbec237e752c1a7217ad57550f5b32
Timestamp: 1721785849 Timestamp [UCT]: 2024-07-24 01:50:49 Age [y:d:h:m:s]: 00:280:12:06:57
Block: 1072353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200414 RingCT/type: yes/0
Extra: 01b016c95d982366316d8e109fdde8739a85fbec237e752c1a7217ad57550f5b3202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dc2de0d335f969f8bd0ce3cdcdafd9268e53a22b7a7a74612b54e7eaa590602 0.600000000000 1544816 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": 1072363, "vin": [ { "gen": { "height": 1072353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dc2de0d335f969f8bd0ce3cdcdafd9268e53a22b7a7a74612b54e7eaa590602" } } ], "extra": [ 1, 176, 22, 201, 93, 152, 35, 102, 49, 109, 142, 16, 159, 221, 232, 115, 154, 133, 251, 236, 35, 126, 117, 44, 26, 114, 23, 173, 87, 85, 15, 91, 50, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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