Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3decac730c522f8b97d34848a8b4105f1f6d2de2a004fadc97076b346e192d8b

Tx prefix hash: 51690fad279d5aef7a910307d474155b8f6b4da29304e3d6aa8cc0794aa3ef47
Tx public key: aee8e99ef6d662555605e505ee1f6d4815145f0fcdc0b02851278385d5782da6
Timestamp: 1689543424 Timestamp [UCT]: 2023-07-16 21:37:04 Age [y:d:h:m:s]: 01:226:15:56:11
Block: 805317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423083 RingCT/type: yes/0
Extra: 01aee8e99ef6d662555605e505ee1f6d4815145f0fcdc0b02851278385d5782da602110000000775e3f0e9000000000000000000

1 output(s) for total of 1.317196591000 dcy

stealth address amount amount idx
00: 3038acdd230d4e5c6db571c415eeaacca8f8459426c3bff66f19acacbd86459f 1.317196591000 1256542 of 0

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": 805327, "vin": [ { "gen": { "height": 805317 } } ], "vout": [ { "amount": 1317196591, "target": { "key": "3038acdd230d4e5c6db571c415eeaacca8f8459426c3bff66f19acacbd86459f" } } ], "extra": [ 1, 174, 232, 233, 158, 246, 214, 98, 85, 86, 5, 229, 5, 238, 31, 109, 72, 21, 20, 95, 15, 205, 192, 176, 40, 81, 39, 131, 133, 213, 120, 45, 166, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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