Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bab57040638e7290d78a9ff46e4861c5708752c7a308ca1f6c36d4bfb27e361b

Tx prefix hash: 517b92ad9ef2387ccea36de320b8828208c3e323eef5288abddd415097c97aa5
Tx public key: f3e2d4ccb32569d05da79c4e49cff29a6f30d18a742c943b0d2c270b0ae80b65
Timestamp: 1577016762 Timestamp [UCT]: 2019-12-22 12:12:42 Age [y:d:h:m:s]: 05:011:18:16:32
Block: 29619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158067 RingCT/type: yes/0
Extra: 01f3e2d4ccb32569d05da79c4e49cff29a6f30d18a742c943b0d2c270b0ae80b650211000000024943cd9f000000000000000000

1 output(s) for total of 489.621883704000 dcy

stealth address amount amount idx
00: 9ea7124b419a8da2b8fd4dac5f10bd16323b1e2a924da770c81bc2965eac2cdf 489.621883704000 48737 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": 29629, "vin": [ { "gen": { "height": 29619 } } ], "vout": [ { "amount": 489621883704, "target": { "key": "9ea7124b419a8da2b8fd4dac5f10bd16323b1e2a924da770c81bc2965eac2cdf" } } ], "extra": [ 1, 243, 226, 212, 204, 179, 37, 105, 208, 93, 167, 156, 78, 73, 207, 242, 154, 111, 48, 209, 138, 116, 44, 148, 59, 13, 44, 39, 11, 10, 232, 11, 101, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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