Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7664b9e49e5d0f7e17544bf0b1fa1479114f527cb76815b3cbd6c990c43ae22d

Tx prefix hash: 8661f0170cdaf112b9bbf8a66db6cbc58782b6eab5ba4251c3a02cf52b402cb8
Tx public key: b6ef38a7fc154a0ae52457e62c2af08abd83ea3ae53d11d1951f1b10167b354e
Timestamp: 1701000394 Timestamp [UCT]: 2023-11-26 12:06:34 Age [y:d:h:m:s]: 01:169:03:45:16
Block: 900035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382085 RingCT/type: yes/0
Extra: 01b6ef38a7fc154a0ae52457e62c2af08abd83ea3ae53d11d1951f1b10167b354e02110000001075e3f0e9000000000000000000

1 output(s) for total of 0.639455616000 dcy

stealth address amount amount idx
00: a9f3bb7287511f4cebe422fa4dbcf58e1ea2c0258e1e42c471acbb4866f45eda 0.639455616000 1356512 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": 900045, "vin": [ { "gen": { "height": 900035 } } ], "vout": [ { "amount": 639455616, "target": { "key": "a9f3bb7287511f4cebe422fa4dbcf58e1ea2c0258e1e42c471acbb4866f45eda" } } ], "extra": [ 1, 182, 239, 56, 167, 252, 21, 74, 10, 229, 36, 87, 230, 44, 42, 240, 138, 189, 131, 234, 58, 229, 61, 17, 209, 149, 31, 27, 16, 22, 123, 53, 78, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 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