Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f01cbc32533ef13d0917ceea878380809091eb302b5bcf46a358d8cc652e19

Tx prefix hash: a73f4d7c8508731ba3432136a2370a1efc33912bdb361d2a638a150e1ed4a2ec
Tx public key: 2bdf2d06af29d8ec1bfa234338b3b5cd0c9154a85e59c258075aa4c93e8ab7ac
Timestamp: 1725139796 Timestamp [UCT]: 2024-08-31 21:29:56 Age [y:d:h:m:s]: 00:238:21:38:17
Block: 1100162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170616 RingCT/type: yes/0
Extra: 012bdf2d06af29d8ec1bfa234338b3b5cd0c9154a85e59c258075aa4c93e8ab7ac02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 919abdd5713693809c7d5c64d2e2a8fa3cebb5d1ed67da1a22a9212ad0ed7570 0.600000000000 1576135 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": 1100172, "vin": [ { "gen": { "height": 1100162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "919abdd5713693809c7d5c64d2e2a8fa3cebb5d1ed67da1a22a9212ad0ed7570" } } ], "extra": [ 1, 43, 223, 45, 6, 175, 41, 216, 236, 27, 250, 35, 67, 56, 179, 181, 205, 12, 145, 84, 168, 94, 89, 194, 88, 7, 90, 164, 201, 62, 138, 183, 172, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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