Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59bab4cfd18eb055df3e79a1877467d6feef5f9a2b0c7fe61801cf9c37ae9767

Tx prefix hash: 251b7b5a50409b20d6d34d7f322e3a7530c12e7c8200ef8761163d00ee74908e
Tx public key: 7f46c0371e15daddeb23520c7fd21c8aa00645419aa4d75d444ca86883f1d3b6
Timestamp: 1714986171 Timestamp [UCT]: 2024-05-06 09:02:51 Age [y:d:h:m:s]: 01:042:01:59:40
Block: 1015987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290924 RingCT/type: yes/0
Extra: 017f46c0371e15daddeb23520c7fd21c8aa00645419aa4d75d444ca86883f1d3b602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc30787d232cc4a717895675f0d4b9013d379f2e15cd185a540870e8e6071aa5 0.600000000000 1479442 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": 1015997, "vin": [ { "gen": { "height": 1015987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc30787d232cc4a717895675f0d4b9013d379f2e15cd185a540870e8e6071aa5" } } ], "extra": [ 1, 127, 70, 192, 55, 30, 21, 218, 221, 235, 35, 82, 12, 127, 210, 28, 138, 160, 6, 69, 65, 154, 164, 215, 93, 68, 76, 168, 104, 131, 241, 211, 182, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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