Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a28c8b6881bcbd192d192916c581baecb88e6705a1a8470680cf74bb39a2e91

Tx prefix hash: eb0f5fe0730abdc12828de96f3c0396f87f1fee5a8874aabb931bc5faa9513cd
Tx public key: da6a9eb8faf7aa372710c25de6e0025639244ad6201040b323452cdf9b41af0b
Timestamp: 1702994684 Timestamp [UCT]: 2023-12-19 14:04:44 Age [y:d:h:m:s]: 01:149:23:45:21
Block: 916578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368349 RingCT/type: yes/0
Extra: 01da6a9eb8faf7aa372710c25de6e0025639244ad6201040b323452cdf9b41af0b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e1a8f4b3cce1fac7366ced16c6c9b7505c0b00c5046a6ec770c05e80f411b4 0.600000000000 1374136 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": 916588, "vin": [ { "gen": { "height": 916578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e1a8f4b3cce1fac7366ced16c6c9b7505c0b00c5046a6ec770c05e80f411b4" } } ], "extra": [ 1, 218, 106, 158, 184, 250, 247, 170, 55, 39, 16, 194, 93, 230, 224, 2, 86, 57, 36, 74, 214, 32, 16, 64, 179, 35, 69, 44, 223, 155, 65, 175, 11, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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