Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bc1502276850e54d0c5feab35c36811f401ea0fa0c9d02af94b59b14da09a2c

Tx prefix hash: 28044d26475d6374d9b66735ce903c3c80419664e85e61b99f433b495170cdec
Tx public key: 565519344c745d4b49f59e509ede075eae36dce84153aadf3ef96b5a912f284e
Timestamp: 1736966618 Timestamp [UCT]: 2025-01-15 18:43:38 Age [y:d:h:m:s]: 00:334:20:48:51
Block: 1198062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236873 RingCT/type: yes/0
Extra: 01565519344c745d4b49f59e509ede075eae36dce84153aadf3ef96b5a912f284e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b06516f08f22a8a979b99db4e2fd4c6655606144e31e23c2c2a3a60df1cac1b 0.600000000000 1684679 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": 1198072, "vin": [ { "gen": { "height": 1198062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b06516f08f22a8a979b99db4e2fd4c6655606144e31e23c2c2a3a60df1cac1b" } } ], "extra": [ 1, 86, 85, 25, 52, 76, 116, 93, 75, 73, 245, 158, 80, 158, 222, 7, 94, 174, 54, 220, 232, 65, 83, 170, 223, 62, 249, 107, 90, 145, 47, 40, 78, 2, 17, 0, 0, 0, 2, 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