Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b066576808062ecff567b294b76312bd3ebdc53e2b2d3f54fb5d139e8be143bc

Tx prefix hash: 61dbe62fb8f94382ffa919a0fd574bd492dd248b88de904acd9285e01b693bdf
Tx public key: d95d7960594b157c6b91fd24212c6441df4e08d766825b4a92b42eb7bea816e9
Timestamp: 1673531475 Timestamp [UCT]: 2023-01-12 13:51:15 Age [y:d:h:m:s]: 02:303:07:13:50
Block: 673169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736168 RingCT/type: yes/0
Extra: 01d95d7960594b157c6b91fd24212c6441df4e08d766825b4a92b42eb7bea816e90211000000018b7b6602000000000000000000

1 output(s) for total of 3.610036640000 dcy

stealth address amount amount idx
00: 3d174c241fa8126685ae47509f062ec938ea1095400242dbf240ee853e818168 3.610036640000 1114762 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": 673179, "vin": [ { "gen": { "height": 673169 } } ], "vout": [ { "amount": 3610036640, "target": { "key": "3d174c241fa8126685ae47509f062ec938ea1095400242dbf240ee853e818168" } } ], "extra": [ 1, 217, 93, 121, 96, 89, 75, 21, 124, 107, 145, 253, 36, 33, 44, 100, 65, 223, 78, 8, 215, 102, 130, 91, 74, 146, 180, 46, 183, 190, 168, 22, 233, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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