Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b82e1066e2346b52bb84dff7c45a90a8c768734e3832221f491594deda48fdbb

Tx prefix hash: 320e66c250ce6eeddda1e218515e308612a1566dc72a8ea46c20859a76f2884e
Tx public key: 59fcb7d231fd4ccdae01d3ea2eeec3b1e736a93cf959358184b429cdd80689a5
Timestamp: 1637370656 Timestamp [UCT]: 2021-11-20 01:10:56 Age [y:d:h:m:s]: 03:044:21:14:01
Block: 377955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 810929 RingCT/type: yes/0
Extra: 0159fcb7d231fd4ccdae01d3ea2eeec3b1e736a93cf959358184b429cdd80689a502110000000b379224c2000000000000000000

1 output(s) for total of 34.330376958000 dcy

stealth address amount amount idx
00: 1d46e4cc32a25074036ead4fa63d40b0f6da12a82dd4ccd433925d46dd0c9fb9 34.330376958000 764394 of 0

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": 377965, "vin": [ { "gen": { "height": 377955 } } ], "vout": [ { "amount": 34330376958, "target": { "key": "1d46e4cc32a25074036ead4fa63d40b0f6da12a82dd4ccd433925d46dd0c9fb9" } } ], "extra": [ 1, 89, 252, 183, 210, 49, 253, 76, 205, 174, 1, 211, 234, 46, 238, 195, 177, 231, 54, 169, 60, 249, 89, 53, 129, 132, 180, 41, 205, 216, 6, 137, 165, 2, 17, 0, 0, 0, 11, 55, 146, 36, 194, 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