Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7e2c4f6aae9c41a0fc46e6c0e6cf5f31e498e9e171aea98fffe4e65dc2b29e

Tx prefix hash: ac3ca9a0f28964a4634551dad3730ca9569ef1b7c1927240797f83f7ed8077f5
Tx public key: 42b981fba74454023b510a34c9c0256c36ccaa3d0219d949cc803e51dcd2d9b3
Timestamp: 1671986642 Timestamp [UCT]: 2022-12-25 16:44:02 Age [y:d:h:m:s]: 02:113:01:04:06
Block: 660380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602482 RingCT/type: yes/0
Extra: 0142b981fba74454023b510a34c9c0256c36ccaa3d0219d949cc803e51dcd2d9b3021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.980035030000 dcy

stealth address amount amount idx
00: 6bf07d44f37089ec0ca7c2ad4dbb588ba92b1f78cb87b33303b9e32fd29318f1 3.980035030000 1101113 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": 660390, "vin": [ { "gen": { "height": 660380 } } ], "vout": [ { "amount": 3980035030, "target": { "key": "6bf07d44f37089ec0ca7c2ad4dbb588ba92b1f78cb87b33303b9e32fd29318f1" } } ], "extra": [ 1, 66, 185, 129, 251, 167, 68, 84, 2, 59, 81, 10, 52, 201, 192, 37, 108, 54, 204, 170, 61, 2, 25, 217, 73, 204, 128, 62, 81, 220, 210, 217, 179, 2, 17, 0, 0, 0, 1, 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