Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78a3ed373e87ba6253f426acc500e63f52d5a2655c528468d3549c15e772e1c7

Tx prefix hash: 422043964f029e83088433d5b6284b554b4e3c1d28576c964bf6a29e64409f45
Tx public key: b22675e51b1d8922bbf920ff916c73f8a8290e0bd40ee0d98b0c2fc220dcb6ec
Timestamp: 1630806716 Timestamp [UCT]: 2021-09-05 01:51:56 Age [y:d:h:m:s]: 04:060:21:36:53
Block: 327642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076750 RingCT/type: yes/0
Extra: 01b22675e51b1d8922bbf920ff916c73f8a8290e0bd40ee0d98b0c2fc220dcb6ec02110000002048397882000000000000000000

1 output(s) for total of 50.394889043000 dcy

stealth address amount amount idx
00: b2728353e86ef4054016446ed41a3055d57f3775c901ee7988415e5ac59f0997 50.394889043000 678479 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": 327652, "vin": [ { "gen": { "height": 327642 } } ], "vout": [ { "amount": 50394889043, "target": { "key": "b2728353e86ef4054016446ed41a3055d57f3775c901ee7988415e5ac59f0997" } } ], "extra": [ 1, 178, 38, 117, 229, 27, 29, 137, 34, 187, 249, 32, 255, 145, 108, 115, 248, 168, 41, 14, 11, 212, 14, 224, 217, 139, 12, 47, 194, 32, 220, 182, 236, 2, 17, 0, 0, 0, 32, 72, 57, 120, 130, 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