Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71368c593ad9ff53ce2e69d49b6ffd105767e79f34b4c89c5ded05c55277473

Tx prefix hash: 2303247db0f8423c018aa1d71b26c8a19e1d5005be4b78c21fbf26b07eea4825
Tx public key: 6682346f2573f0e49f516ba67d1145e2b5a09ea7abda713f165b80e44e3a422a
Timestamp: 1736778833 Timestamp [UCT]: 2025-01-13 14:33:53 Age [y:d:h:m:s]: 00:065:07:31:58
Block: 1196510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46485 RingCT/type: yes/0
Extra: 016682346f2573f0e49f516ba67d1145e2b5a09ea7abda713f165b80e44e3a422a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c0adbf6a737fb280acbba7673c45f01aeb0dde3efa6f2033abfd12530f0753 0.600000000000 1683109 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": 1196520, "vin": [ { "gen": { "height": 1196510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c0adbf6a737fb280acbba7673c45f01aeb0dde3efa6f2033abfd12530f0753" } } ], "extra": [ 1, 102, 130, 52, 111, 37, 115, 240, 228, 159, 81, 107, 166, 125, 17, 69, 226, 181, 160, 158, 167, 171, 218, 113, 63, 22, 91, 128, 228, 78, 58, 66, 42, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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