Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ae84e826069cb94e1c5ca6161277e3883de5f4c57aae69313c19b1afb8c68a

Tx prefix hash: 8dbf927285bdab38e8a2ad4c3b362cd9fa323177506ee8739fb976a2a412489c
Tx public key: 8d819e2871e50d2f21e1996f54045edcb1c84a5e6a37cbe4ef2e3a2a799e2b24
Timestamp: 1723144333 Timestamp [UCT]: 2024-08-08 19:12:13 Age [y:d:h:m:s]: 00:150:18:57:11
Block: 1083617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107888 RingCT/type: yes/0
Extra: 018d819e2871e50d2f21e1996f54045edcb1c84a5e6a37cbe4ef2e3a2a799e2b24021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf754daf379e6f22be91b9abfd946eee96bd02584f20e69bc549bf6488f1683f 0.600000000000 1557602 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": 1083627, "vin": [ { "gen": { "height": 1083617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf754daf379e6f22be91b9abfd946eee96bd02584f20e69bc549bf6488f1683f" } } ], "extra": [ 1, 141, 129, 158, 40, 113, 229, 13, 47, 33, 225, 153, 111, 84, 4, 94, 220, 177, 200, 74, 94, 106, 55, 203, 228, 239, 46, 58, 42, 121, 158, 43, 36, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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