Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d43b41162f298fa0677fdc28b2a61cd210c915c0cba7658a3cc51be32fecee6

Tx prefix hash: 0fb7560c9fa2879c064a90871a653b14b0b58917614f376c8eb1ef6963d19bb1
Tx public key: 73b20e07f9308555c1e80250a7eea2c6bcfef925127dfeeda81f78eeb34b9daa
Timestamp: 1719645932 Timestamp [UCT]: 2024-06-29 07:25:32 Age [y:d:h:m:s]: 00:148:07:53:42
Block: 1054621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106157 RingCT/type: yes/0
Extra: 0173b20e07f9308555c1e80250a7eea2c6bcfef925127dfeeda81f78eeb34b9daa0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 502c30e4e1790f2b60e0a168265cb2b73d1a0d763d1d492911f8f0735452e24b 0.600000000000 1524988 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": 1054631, "vin": [ { "gen": { "height": 1054621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "502c30e4e1790f2b60e0a168265cb2b73d1a0d763d1d492911f8f0735452e24b" } } ], "extra": [ 1, 115, 178, 14, 7, 249, 48, 133, 85, 193, 232, 2, 80, 167, 238, 162, 198, 188, 254, 249, 37, 18, 125, 254, 237, 168, 31, 120, 238, 179, 75, 157, 170, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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