Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9d5a31c62563f58ca23a7b2ebcdadb6c6da6996861a03b10eb07adcb151d35

Tx prefix hash: b80afb32398695e81b81aa9810e060e4d8f29600d1223aed5a3e428f8ca2adaa
Tx public key: 5bb77324d60a0ca8f8dfa31920cfd8327ef66a7606901f86d247c71e3dd7d84a
Timestamp: 1702235057 Timestamp [UCT]: 2023-12-10 19:04:17 Age [y:d:h:m:s]: 01:136:01:38:15
Block: 910276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358404 RingCT/type: yes/0
Extra: 015bb77324d60a0ca8f8dfa31920cfd8327ef66a7606901f86d247c71e3dd7d84a021100000014e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa4ca4ff40ceea016a913296a71f8868ab1d149bd56f0201ae7d1a422419bec 0.600000000000 1367425 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": 910286, "vin": [ { "gen": { "height": 910276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa4ca4ff40ceea016a913296a71f8868ab1d149bd56f0201ae7d1a422419bec" } } ], "extra": [ 1, 91, 183, 115, 36, 214, 10, 12, 168, 248, 223, 163, 25, 32, 207, 216, 50, 126, 246, 106, 118, 6, 144, 31, 134, 210, 71, 199, 30, 61, 215, 216, 74, 2, 17, 0, 0, 0, 20, 230, 210, 127, 156, 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