Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f5d013992cdfdff80c80ab79e70b6631139538e036c077fa65e01b5337822a

Tx prefix hash: 892e474a4502e69919e704cc9e192721ff3dcdbcb776befe2c93a1dd65bd2390
Tx public key: fe3f18dc981d2abdc59d818259a46238fb8a1ec3f71d3f66730568fa7e679dde
Timestamp: 1696889602 Timestamp [UCT]: 2023-10-09 22:13:22 Age [y:d:h:m:s]: 01:204:08:34:45
Block: 866163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407094 RingCT/type: yes/0
Extra: 01fe3f18dc981d2abdc59d818259a46238fb8a1ec3f71d3f66730568fa7e679dde02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.828023100000 dcy

stealth address amount amount idx
00: e7082fbfcfee1151d1f19f66342b2fc1ce7a132dd1ac6487dfa0ead4bc078f9b 0.828023100000 1320735 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": 866173, "vin": [ { "gen": { "height": 866163 } } ], "vout": [ { "amount": 828023100, "target": { "key": "e7082fbfcfee1151d1f19f66342b2fc1ce7a132dd1ac6487dfa0ead4bc078f9b" } } ], "extra": [ 1, 254, 63, 24, 220, 152, 29, 42, 189, 197, 157, 129, 130, 89, 164, 98, 56, 251, 138, 30, 195, 247, 29, 63, 102, 115, 5, 104, 250, 126, 103, 157, 222, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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