Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b279356c976fcce6eef1b3ff2d3e39e6c24d4c8c99cf35e6b723a86280710891

Tx prefix hash: fcdabe6456c2bb22467b456c64acfc1454588d7ce0c2b105403b9214cb15dc3c
Tx public key: 7cc441066861eae8c700c4a5a493e673c71087080b7826915cf1fc37468d7c33
Timestamp: 1735269293 Timestamp [UCT]: 2024-12-27 03:14:53 Age [y:d:h:m:s]: 00:086:02:10:20
Block: 1184019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61318 RingCT/type: yes/0
Extra: 017cc441066861eae8c700c4a5a493e673c71087080b7826915cf1fc37468d7c330211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20b76471e7e156e040845a1dd94060efc2d5287186744901698c5c436d2a82e9 0.600000000000 1670470 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": 1184029, "vin": [ { "gen": { "height": 1184019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20b76471e7e156e040845a1dd94060efc2d5287186744901698c5c436d2a82e9" } } ], "extra": [ 1, 124, 196, 65, 6, 104, 97, 234, 232, 199, 0, 196, 165, 164, 147, 230, 115, 199, 16, 135, 8, 11, 120, 38, 145, 92, 241, 252, 55, 70, 141, 124, 51, 2, 17, 0, 0, 0, 5, 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