Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33555831d9f3f1b7a54d114e546a1de4ffe40a170f209d780b4c15eb78249fb1

Tx prefix hash: 101f55f894a317830e8cabc0d18d2ed5bbfc0a11ba1043aab3a3488385e1af1a
Tx public key: b5c4e7b10c5fef1a2806dcaf984e8509a39053c3821d41dfbfebf4ab3be5b43a
Timestamp: 1638816943 Timestamp [UCT]: 2021-12-06 18:55:43 Age [y:d:h:m:s]: 03:333:07:47:52
Block: 389853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1014639 RingCT/type: yes/0
Extra: 01b5c4e7b10c5fef1a2806dcaf984e8509a39053c3821d41dfbfebf4ab3be5b43a021100000001e9564d6f000000000000000000

1 output(s) for total of 31.351299119000 dcy

stealth address amount amount idx
00: bd3762258d9be9a79fe407598100648706b0f84913eb4776fdbeaf717a78f3d7 31.351299119000 785278 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": 389863, "vin": [ { "gen": { "height": 389853 } } ], "vout": [ { "amount": 31351299119, "target": { "key": "bd3762258d9be9a79fe407598100648706b0f84913eb4776fdbeaf717a78f3d7" } } ], "extra": [ 1, 181, 196, 231, 177, 12, 95, 239, 26, 40, 6, 220, 175, 152, 78, 133, 9, 163, 144, 83, 195, 130, 29, 65, 223, 191, 235, 244, 171, 59, 229, 180, 58, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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