Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a3a516712c6fd5e8eb1b65bfa119f63e3797d0525b78a93aee2607bd464376c

Tx prefix hash: 54b4cee03b911271cea5b2b0ca90dfbe0690642b80557f3e1b42633a3f2a62a2
Tx public key: b6a6d2a6d2e8be37f5260f9ec14b08970f6a4cf9fe4a99d86ad0e1a2f14bfa08
Timestamp: 1727377326 Timestamp [UCT]: 2024-09-26 19:02:06 Age [y:d:h:m:s]: 00:149:09:35:55
Block: 1118718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106542 RingCT/type: yes/0
Extra: 01b6a6d2a6d2e8be37f5260f9ec14b08970f6a4cf9fe4a99d86ad0e1a2f14bfa08021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75f3ffcc7343387d5f77a4ebbcab5593e6e24717adc2806ab8d4dc9c9964f3cc 0.600000000000 1600009 of 15

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": 1118728, "vin": [ { "gen": { "height": 1118718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75f3ffcc7343387d5f77a4ebbcab5593e6e24717adc2806ab8d4dc9c9964f3cc" } } ], "extra": [ 1, 182, 166, 210, 166, 210, 232, 190, 55, 245, 38, 15, 158, 193, 75, 8, 151, 15, 106, 76, 249, 254, 74, 153, 216, 106, 208, 225, 162, 241, 75, 250, 8, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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