Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9136032c90740779b21ebed23d10329b09c4fc5d3ebd5f5b1fc050a61faa4bb

Tx prefix hash: 53704e2e1b0035e113c43264632a8862d10b1a8b4a6dcc8d30bb3ade10fa51ea
Tx public key: 0aee5e404fad6e24c68fefb01f3dc220fb08191d126210090bee12d14f28d95e
Timestamp: 1682466051 Timestamp [UCT]: 2023-04-25 23:40:51 Age [y:d:h:m:s]: 01:356:20:57:25
Block: 746634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516317 RingCT/type: yes/0
Extra: 010aee5e404fad6e24c68fefb01f3dc220fb08191d126210090bee12d14f28d95e021100000002e7ace25d000000000000000000

1 output(s) for total of 2.061065642000 dcy

stealth address amount amount idx
00: 40481a7172f6f2a01a57ed106672d275421e374b2c73d898ac44d8a646a3535c 2.061065642000 1194215 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": 746644, "vin": [ { "gen": { "height": 746634 } } ], "vout": [ { "amount": 2061065642, "target": { "key": "40481a7172f6f2a01a57ed106672d275421e374b2c73d898ac44d8a646a3535c" } } ], "extra": [ 1, 10, 238, 94, 64, 79, 173, 110, 36, 198, 143, 239, 176, 31, 61, 194, 32, 251, 8, 25, 29, 18, 98, 16, 9, 11, 238, 18, 209, 79, 40, 217, 94, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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