Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca9b14e82927cdb7aa624b2282fb8157a306938bd411b826ca70ebc2ea4a4bf

Tx prefix hash: bff54135147c57625b0e5fcb89a2044d278c5d7ebc9928efe491f6662526a3a6
Tx public key: fdb54cdfcd63267f9d452303af1be881223aedd0f23c5ad365dbd3075353af3b
Timestamp: 1634312837 Timestamp [UCT]: 2021-10-15 15:47:17 Age [y:d:h:m:s]: 03:150:07:11:08
Block: 353640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 885076 RingCT/type: yes/0
Extra: 01fdb54cdfcd63267f9d452303af1be881223aedd0f23c5ad365dbd3075353af3b02110000001836fe6557000000000000000000

1 output(s) for total of 41.327991101000 dcy

stealth address amount amount idx
00: 51a5c05eaad270d217fff0553f755407cbf0caa3690d9f1e5eb78c1f60cb1b54 41.327991101000 722600 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": 353650, "vin": [ { "gen": { "height": 353640 } } ], "vout": [ { "amount": 41327991101, "target": { "key": "51a5c05eaad270d217fff0553f755407cbf0caa3690d9f1e5eb78c1f60cb1b54" } } ], "extra": [ 1, 253, 181, 76, 223, 205, 99, 38, 127, 157, 69, 35, 3, 175, 27, 232, 129, 34, 58, 237, 208, 242, 60, 90, 211, 101, 219, 211, 7, 83, 83, 175, 59, 2, 17, 0, 0, 0, 24, 54, 254, 101, 87, 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