Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebd53cbec8b7be0627c5b75bfb4c435da3c175c1180d3d29bcb29782b88f7a67

Tx prefix hash: 7c557a7670f8693f040cbaa075baaf07ac4d542f3eb8793c2005941050902b25
Tx public key: 117b4e9a268197cac18716b4de8ac843b8c8b8c702cc85bebdc6f19aa41650c0
Timestamp: 1637872441 Timestamp [UCT]: 2021-11-25 20:34:01 Age [y:d:h:m:s]: 03:006:09:31:15
Block: 382053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783461 RingCT/type: yes/0
Extra: 01117b4e9a268197cac18716b4de8ac843b8c8b8c702cc85bebdc6f19aa41650c0021100000003e9564d6f000000000000000000

1 output(s) for total of 33.274210612000 dcy

stealth address amount amount idx
00: a9447e908a409f106ae68fbaf2dfa8802006aebb8aeec147f8797110d4605941 33.274210612000 771660 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": 382063, "vin": [ { "gen": { "height": 382053 } } ], "vout": [ { "amount": 33274210612, "target": { "key": "a9447e908a409f106ae68fbaf2dfa8802006aebb8aeec147f8797110d4605941" } } ], "extra": [ 1, 17, 123, 78, 154, 38, 129, 151, 202, 193, 135, 22, 180, 222, 138, 200, 67, 184, 200, 184, 199, 2, 204, 133, 190, 189, 198, 241, 154, 164, 22, 80, 192, 2, 17, 0, 0, 0, 3, 233, 86, 77, 111, 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