Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cb3fbcba586dff192c7ff661403ccbb6e682d9eb9f799b318fa4c5c8068c107

Tx prefix hash: 51a23c4227cab5712aa5e92f25f59bb07f078fadfe8e1fbcb4b44f63024c512a
Tx public key: e7ef3990f66bf1d610863e94ea391a1a44425045ac4e8053607e5b31968ea5c5
Timestamp: 1730092707 Timestamp [UCT]: 2024-10-28 05:18:27 Age [y:d:h:m:s]: 00:186:13:25:33
Block: 1141166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133170 RingCT/type: yes/0
Extra: 01e7ef3990f66bf1d610863e94ea391a1a44425045ac4e8053607e5b31968ea5c5021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf949ef13d7eaed14285c230a2a8389463111ab71f4fe9c01113f4fcde976b6b 0.600000000000 1624973 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": 1141176, "vin": [ { "gen": { "height": 1141166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf949ef13d7eaed14285c230a2a8389463111ab71f4fe9c01113f4fcde976b6b" } } ], "extra": [ 1, 231, 239, 57, 144, 246, 107, 241, 214, 16, 134, 62, 148, 234, 57, 26, 26, 68, 66, 80, 69, 172, 78, 128, 83, 96, 126, 91, 49, 150, 142, 165, 197, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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