Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ec0a3c90603fd929f9975f5b95ab61e44be2819b3cbfdb51f7113a8dfc2961

Tx prefix hash: e1fb5d0cdf1c2ed114f9898aa784855e7a6d1c84a5d0a0a725991f86b41b6682
Tx public key: 13d89485807775494d610ea86e8b1bce094b5a5aa552715c3bf82af90585690d
Timestamp: 1713528446 Timestamp [UCT]: 2024-04-19 12:07:26 Age [y:d:h:m:s]: 00:350:04:54:10
Block: 1003896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250364 RingCT/type: yes/0
Extra: 0113d89485807775494d610ea86e8b1bce094b5a5aa552715c3bf82af90585690d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ffa1ceffcf67fabae25cb79d037aa150603959aaa409444ce3a26855b478b80 0.600000000000 1464446 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": 1003906, "vin": [ { "gen": { "height": 1003896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ffa1ceffcf67fabae25cb79d037aa150603959aaa409444ce3a26855b478b80" } } ], "extra": [ 1, 19, 216, 148, 133, 128, 119, 117, 73, 77, 97, 14, 168, 110, 139, 27, 206, 9, 75, 90, 90, 165, 82, 113, 92, 59, 248, 42, 249, 5, 133, 105, 13, 2, 17, 0, 0, 0, 5, 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