Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db1e6e68884bc29498b2c7ba310362fe724ce5bf666286ddb6e4066fccc7ca9

Tx prefix hash: ed9efd04bbcbfc6c16de31784904837f36427155dbe678a9f6fcf3bd1ffa1e3b
Tx public key: 2b32b0d435cdc49e4d4f1b1e684ece16e5c738b7f880ec6d18dad6c3ca07a28a
Timestamp: 1730781673 Timestamp [UCT]: 2024-11-05 04:41:13 Age [y:d:h:m:s]: 00:143:19:29:54
Block: 1146845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102626 RingCT/type: yes/0
Extra: 012b32b0d435cdc49e4d4f1b1e684ece16e5c738b7f880ec6d18dad6c3ca07a28a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819e1322fd435c92b9413e1b56533d89090e0395c751b088ca44cafda303b521 0.600000000000 1631536 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": 1146855, "vin": [ { "gen": { "height": 1146845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819e1322fd435c92b9413e1b56533d89090e0395c751b088ca44cafda303b521" } } ], "extra": [ 1, 43, 50, 176, 212, 53, 205, 196, 158, 77, 79, 27, 30, 104, 78, 206, 22, 229, 199, 56, 183, 248, 128, 236, 109, 24, 218, 214, 195, 202, 7, 162, 138, 2, 17, 0, 0, 0, 2, 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