Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a39057df9805821ac87e9d3d84767497bd615366a5dd0aac2875edeb9143a775

Tx prefix hash: 71b1e23407867a22ec88d0dcc2c3a9188a69005fec48690b1fb1b53d1f147a74
Tx public key: 773efcb2c444698e5c984983a25f40ba2ed6abba6d3dcc6a064ad462798acb89
Timestamp: 1626885994 Timestamp [UCT]: 2021-07-21 16:46:34 Age [y:d:h:m:s]: 03:161:05:51:08
Block: 298357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 886954 RingCT/type: yes/0
Extra: 01773efcb2c444698e5c984983a25f40ba2ed6abba6d3dcc6a064ad462798acb89021100000016733f0e1c000000000000000000

1 output(s) for total of 63.011511581000 dcy

stealth address amount amount idx
00: 03fb6379e2a9b5e4d1592825e255bff403e7eb1fee454a4abae9cf517f316d66 63.011511581000 624200 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": 298367, "vin": [ { "gen": { "height": 298357 } } ], "vout": [ { "amount": 63011511581, "target": { "key": "03fb6379e2a9b5e4d1592825e255bff403e7eb1fee454a4abae9cf517f316d66" } } ], "extra": [ 1, 119, 62, 252, 178, 196, 68, 105, 142, 92, 152, 73, 131, 162, 95, 64, 186, 46, 214, 171, 186, 109, 61, 204, 106, 6, 74, 212, 98, 121, 138, 203, 137, 2, 17, 0, 0, 0, 22, 115, 63, 14, 28, 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