Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22d48d9ec308fbcfc293412d9d61f93a9822f0a96813713d041390ba299847a

Tx prefix hash: 434f46636e38e7d44b0ce5c6f520db8250aded59ef4cc0233e8875405b7d5b1d
Tx public key: 0fb2eeb2f6be7fd11befebe90efdba7786fe764a1a966483d44dec58bcd1a8cd
Timestamp: 1581428722 Timestamp [UCT]: 2020-02-11 13:45:22 Age [y:d:h:m:s]: 04:322:03:15:49
Block: 62690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122452 RingCT/type: yes/0
Extra: 010fb2eeb2f6be7fd11befebe90efdba7786fe764a1a966483d44dec58bcd1a8cd02110000000303d36d11000000000000000000

1 output(s) for total of 380.437063263000 dcy

stealth address amount amount idx
00: 6ed17abaa4fe29784b3dc0ae3e0cde75c366d49d7ebed730d236a14e2f526a90 380.437063263000 115682 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": 62700, "vin": [ { "gen": { "height": 62690 } } ], "vout": [ { "amount": 380437063263, "target": { "key": "6ed17abaa4fe29784b3dc0ae3e0cde75c366d49d7ebed730d236a14e2f526a90" } } ], "extra": [ 1, 15, 178, 238, 178, 246, 190, 127, 209, 27, 239, 235, 233, 14, 253, 186, 119, 134, 254, 118, 74, 26, 150, 100, 131, 212, 77, 236, 88, 188, 209, 168, 205, 2, 17, 0, 0, 0, 3, 3, 211, 109, 17, 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