Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986388ccbe8d60f4a5d1f75edb3fa90dbe9e52eab532973338bcfe6ee81e2fa1

Tx prefix hash: 8930d588dd6cd58b367adec082b787e5463f1487539b9f287e28c506c1853376
Tx public key: a4a043c4c773d621fb0cdb70c07927fed99df1157ec4057dc7d0bc50016ae197
Timestamp: 1696179002 Timestamp [UCT]: 2023-10-01 16:50:02 Age [y:d:h:m:s]: 02:038:03:09:55
Block: 860268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546891 RingCT/type: yes/0
Extra: 01a4a043c4c773d621fb0cdb70c07927fed99df1157ec4057dc7d0bc50016ae19702110000000a4b8f5122000000000000000000

1 output(s) for total of 0.866113969000 dcy

stealth address amount amount idx
00: 367eb8c45d457a4d4f87672942f28def1c5b8cd7b10fcdc77b5bc25bcedb8cf6 0.866113969000 1314544 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": 860278, "vin": [ { "gen": { "height": 860268 } } ], "vout": [ { "amount": 866113969, "target": { "key": "367eb8c45d457a4d4f87672942f28def1c5b8cd7b10fcdc77b5bc25bcedb8cf6" } } ], "extra": [ 1, 164, 160, 67, 196, 199, 115, 214, 33, 251, 12, 219, 112, 192, 121, 39, 254, 217, 157, 241, 21, 126, 196, 5, 125, 199, 208, 188, 80, 1, 106, 225, 151, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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