Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c0a08795a880dd963effab4b22affe7c649ab0986afb21677b1bb83f35591e

Tx prefix hash: 781daaed315c42ecac9e95d77b7d3e5938c283457b5e71f654a4d859e2ca6163
Tx public key: afccf9412a938691e24ea3955982909131e82740a0bc6d30d804067173aa41f8
Timestamp: 1634299244 Timestamp [UCT]: 2021-10-15 12:00:44 Age [y:d:h:m:s]: 03:149:12:01:35
Block: 353559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 884472 RingCT/type: yes/0
Extra: 01afccf9412a938691e24ea3955982909131e82740a0bc6d30d804067173aa41f802110000000bfdc024ec000000000000000000

1 output(s) for total of 41.353539003000 dcy

stealth address amount amount idx
00: 0cbef6d086500db727e87880e5506c0e900422e0b8f99a1c32d9b781da0db2a2 41.353539003000 722443 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": 353569, "vin": [ { "gen": { "height": 353559 } } ], "vout": [ { "amount": 41353539003, "target": { "key": "0cbef6d086500db727e87880e5506c0e900422e0b8f99a1c32d9b781da0db2a2" } } ], "extra": [ 1, 175, 204, 249, 65, 42, 147, 134, 145, 226, 78, 163, 149, 89, 130, 144, 145, 49, 232, 39, 64, 160, 188, 109, 48, 216, 4, 6, 113, 115, 170, 65, 248, 2, 17, 0, 0, 0, 11, 253, 192, 36, 236, 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