Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 231f451a5482cfd00117a12e6b773557787e9f657f2e51f136769b346142899e

Tx prefix hash: 0b253c0b4ee7ce9a3438e328e811f960e1498fdb099548207c820177c6f72d69
Tx public key: 1be2fb50c9a1a7f827e3b4cff343cb669ba43eb90f2c823af038a564eb63f3ef
Timestamp: 1574734905 Timestamp [UCT]: 2019-11-26 02:21:45 Age [y:d:h:m:s]: 05:035:16:37:04
Block: 17590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168324 RingCT/type: yes/0
Extra: 011be2fb50c9a1a7f827e3b4cff343cb669ba43eb90f2c823af038a564eb63f3ef021100000016354bbe3b000000000000000000

1 output(s) for total of 536.683086052000 dcy

stealth address amount amount idx
00: fd4f26cc2aa330c2494cf18329a5ac5a08a2fcff4c067d9f925b1ff706531d13 536.683086052000 25794 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": 17600, "vin": [ { "gen": { "height": 17590 } } ], "vout": [ { "amount": 536683086052, "target": { "key": "fd4f26cc2aa330c2494cf18329a5ac5a08a2fcff4c067d9f925b1ff706531d13" } } ], "extra": [ 1, 27, 226, 251, 80, 201, 161, 167, 248, 39, 227, 180, 207, 243, 67, 203, 102, 155, 164, 62, 185, 15, 44, 130, 58, 240, 56, 165, 100, 235, 99, 243, 239, 2, 17, 0, 0, 0, 22, 53, 75, 190, 59, 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