Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c427d45c966628d174c7c9a19d648a284fc7a51b2c220e97627e2c8a405adc0

Tx prefix hash: 35825f6db7f84fcfba70d325fac57b2a66fa4e4609f2e0d6ca8b68b796a01128
Tx public key: 9ff5a5df42e2791a1356dafd3b56841bc78713f7681ca0ee8763669294fbe2a1
Timestamp: 1624041417 Timestamp [UCT]: 2021-06-18 18:36:57 Age [y:d:h:m:s]: 03:261:14:16:20
Block: 279889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953389 RingCT/type: yes/0
Extra: 019ff5a5df42e2791a1356dafd3b56841bc78713f7681ca0ee8763669294fbe2a102110000008c9c1fbdcc000000000000000000

1 output(s) for total of 72.547026731000 dcy

stealth address amount amount idx
00: 10d0311b9e6f5c077614179ed68055d965bdb4b0b367c68c2f8e0e7afd31ca2c 72.547026731000 586106 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": 279899, "vin": [ { "gen": { "height": 279889 } } ], "vout": [ { "amount": 72547026731, "target": { "key": "10d0311b9e6f5c077614179ed68055d965bdb4b0b367c68c2f8e0e7afd31ca2c" } } ], "extra": [ 1, 159, 245, 165, 223, 66, 226, 121, 26, 19, 86, 218, 253, 59, 86, 132, 27, 199, 135, 19, 247, 104, 28, 160, 238, 135, 99, 102, 146, 148, 251, 226, 161, 2, 17, 0, 0, 0, 140, 156, 31, 189, 204, 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