Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3db86f6ac87d7eb8395a91bd4a0f0c69ee98e3bf9bccbd36b5e85f3f1aca55b

Tx prefix hash: 60558440b88d43708336139a4979a16490c7eb205756e9459fde81f84d6641a7
Tx public key: 4147b0c566dd3fee4f181620a2d8da4b35a4d204bce82e0429c59a9df2e9440e
Timestamp: 1712447811 Timestamp [UCT]: 2024-04-06 23:56:51 Age [y:d:h:m:s]: 01:215:21:46:36
Block: 994914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413005 RingCT/type: yes/0
Extra: 014147b0c566dd3fee4f181620a2d8da4b35a4d204bce82e0429c59a9df2e9440e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d9b387c5c5900c616b011607db7440855bc6a9116486cd66f9b2c9743998313 0.600000000000 1455318 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": 994924, "vin": [ { "gen": { "height": 994914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d9b387c5c5900c616b011607db7440855bc6a9116486cd66f9b2c9743998313" } } ], "extra": [ 1, 65, 71, 176, 197, 102, 221, 63, 238, 79, 24, 22, 32, 162, 216, 218, 75, 53, 164, 210, 4, 188, 232, 46, 4, 41, 197, 154, 157, 242, 233, 68, 14, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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