Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27c1a2b828bd04844a86a5c18705425e2282be6adce50e6d8dcab70b78620beb

Tx prefix hash: 62e5004e5fe8612a05726ec35cadb3b0696220c8a194fddacf6806230e5f399f
Tx public key: a3fd70129ff64a99fa859e054b16eb5eb292f30a874cb617fe78e1068549b02b
Timestamp: 1674430749 Timestamp [UCT]: 2023-01-22 23:39:09 Age [y:d:h:m:s]: 02:123:09:59:30
Block: 680639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609894 RingCT/type: yes/0
Extra: 01a3fd70129ff64a99fa859e054b16eb5eb292f30a874cb617fe78e1068549b02b02110000000183600029000000000000000000

1 output(s) for total of 3.410047182000 dcy

stealth address amount amount idx
00: afdd4c8c2c91ec725ccca30025a8b0cfde7c4396c12570f8a5c23c9d8e5a6d25 3.410047182000 1122698 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": 680649, "vin": [ { "gen": { "height": 680639 } } ], "vout": [ { "amount": 3410047182, "target": { "key": "afdd4c8c2c91ec725ccca30025a8b0cfde7c4396c12570f8a5c23c9d8e5a6d25" } } ], "extra": [ 1, 163, 253, 112, 18, 159, 246, 74, 153, 250, 133, 158, 5, 75, 22, 235, 94, 178, 146, 243, 10, 135, 76, 182, 23, 254, 120, 225, 6, 133, 73, 176, 43, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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