Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f6ab4b37f37d820256b0d474d0f17c6af5854def404b065cb99c50b5b9eef2

Tx prefix hash: c12e88eb9b81e13f6b94bde517a4c6ff7f5cc6802351e4ec6944c3ca4f881632
Tx public key: 4b4415d9645d2c7fe2deae049f0643cbf8bfc5226aa3eadb08e92fb7a358b7de
Timestamp: 1703595730 Timestamp [UCT]: 2023-12-26 13:02:10 Age [y:d:h:m:s]: 01:329:23:01:36
Block: 921558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494661 RingCT/type: yes/0
Extra: 014b4415d9645d2c7fe2deae049f0643cbf8bfc5226aa3eadb08e92fb7a358b7de0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a541eaf2527cd8e919d0cdff5ce1f47f11afa53b1153400c8802c67b5c43d548 0.600000000000 1379246 of 15

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": 921568, "vin": [ { "gen": { "height": 921558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a541eaf2527cd8e919d0cdff5ce1f47f11afa53b1153400c8802c67b5c43d548" } } ], "extra": [ 1, 75, 68, 21, 217, 100, 93, 44, 127, 226, 222, 174, 4, 159, 6, 67, 203, 248, 191, 197, 34, 106, 163, 234, 219, 8, 233, 47, 183, 163, 88, 183, 222, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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