Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5c58387e8644ef1c88d32e443bf8142da308237da2f6928ae5b06f7a85e8ba

Tx prefix hash: e6406af6ac5c28b877bea6c647a4356eaeeabafd3def8940ae361d65dda55a76
Tx public key: a3eaa81ea46c09ea357bd3d88c8857718dee8ed61aa335f6064625611ec4e97a
Timestamp: 1703580079 Timestamp [UCT]: 2023-12-26 08:41:19 Age [y:d:h:m:s]: 01:172:19:22:54
Block: 921421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384572 RingCT/type: yes/0
Extra: 01a3eaa81ea46c09ea357bd3d88c8857718dee8ed61aa335f6064625611ec4e97a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b78cbd3db42386db024ff933a5ce7d30b91887ccd99c9f9d48b1e259d623b27c 0.600000000000 1379109 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": 921431, "vin": [ { "gen": { "height": 921421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b78cbd3db42386db024ff933a5ce7d30b91887ccd99c9f9d48b1e259d623b27c" } } ], "extra": [ 1, 163, 234, 168, 30, 164, 108, 9, 234, 53, 123, 211, 216, 140, 136, 87, 113, 141, 238, 142, 214, 26, 163, 53, 246, 6, 70, 37, 97, 30, 196, 233, 122, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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