Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c0951103dcf23a042190275be0314b423aee429577db75eff496ae12e79b1d

Tx prefix hash: 20ab5018a8294a8b9df2ea3cd0e3d40458b07dfa911745dfe43fb9de8b15e03f
Tx public key: a0fd9b811c051fbd4920dcf0e7c959f5ad352f6b24aa26f12b9c4461100dcfea
Timestamp: 1649833892 Timestamp [UCT]: 2022-04-13 07:11:32 Age [y:d:h:m:s]: 02:221:17:14:00
Block: 479145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678325 RingCT/type: yes/0
Extra: 01a0fd9b811c051fbd4920dcf0e7c959f5ad352f6b24aa26f12b9c4461100dcfea021100000001a8c141c5000000000000000000

1 output(s) for total of 15.863315013000 dcy

stealth address amount amount idx
00: 3389f713f345af454c5676d566082455286f59820576a8dab7466d5a356421f4 15.863315013000 899986 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": 479155, "vin": [ { "gen": { "height": 479145 } } ], "vout": [ { "amount": 15863315013, "target": { "key": "3389f713f345af454c5676d566082455286f59820576a8dab7466d5a356421f4" } } ], "extra": [ 1, 160, 253, 155, 129, 28, 5, 31, 189, 73, 32, 220, 240, 231, 201, 89, 245, 173, 53, 47, 107, 36, 170, 38, 241, 43, 156, 68, 97, 16, 13, 207, 234, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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