Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6062f93f4bb6b99f1307c76431da9c6c8ffadaad288500557dceaffa99e8837

Tx prefix hash: baebbced78fe00fa799bbff5d80069b4b9bfad750d844a640a1f057e01f3ef50
Tx public key: 30fbccb9268eaf7b5b08f5a8942590403cfab489c6e7fd8c57d310f7125591aa
Timestamp: 1576643231 Timestamp [UCT]: 2019-12-18 04:27:11 Age [y:d:h:m:s]: 05:022:07:49:59
Block: 28104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164050 RingCT/type: yes/0
Extra: 0130fbccb9268eaf7b5b08f5a8942590403cfab489c6e7fd8c57d310f7125591aa02110000000ead433a0b000000000000000000

1 output(s) for total of 495.314049147000 dcy

stealth address amount amount idx
00: 7ed1a9fa99c472fb4acdd1dd94aa749185ddb4d8eb6abac30ee5679d87fbd0d7 495.314049147000 46626 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": 28114, "vin": [ { "gen": { "height": 28104 } } ], "vout": [ { "amount": 495314049147, "target": { "key": "7ed1a9fa99c472fb4acdd1dd94aa749185ddb4d8eb6abac30ee5679d87fbd0d7" } } ], "extra": [ 1, 48, 251, 204, 185, 38, 142, 175, 123, 91, 8, 245, 168, 148, 37, 144, 64, 60, 250, 180, 137, 198, 231, 253, 140, 87, 211, 16, 247, 18, 85, 145, 170, 2, 17, 0, 0, 0, 14, 173, 67, 58, 11, 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