Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc4d5a27ee17397a119cca56591a2ff9e1f6a0fcfb819ff8ab2fb2ba1ab390e

Tx prefix hash: 5c02689bfa25ba8e4f5e84eeb9bcbb7f1749d54584de06fa13bff9a27f9dcdee
Tx public key: 0b5458510f4b8c0bc415d3477180059fe9b4214a81e76b1407571167a7384303
Timestamp: 1715015226 Timestamp [UCT]: 2024-05-06 17:07:06 Age [y:d:h:m:s]: 00:287:08:36:32
Block: 1016235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205354 RingCT/type: yes/0
Extra: 010b5458510f4b8c0bc415d3477180059fe9b4214a81e76b1407571167a73843030211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db0a0a6c6ff4ccca69c47cf47886d5127d1d3b41ceb1c35ac0f69b5a6acdc1a4 0.600000000000 1479758 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": 1016245, "vin": [ { "gen": { "height": 1016235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db0a0a6c6ff4ccca69c47cf47886d5127d1d3b41ceb1c35ac0f69b5a6acdc1a4" } } ], "extra": [ 1, 11, 84, 88, 81, 15, 75, 140, 11, 196, 21, 211, 71, 113, 128, 5, 159, 233, 180, 33, 74, 129, 231, 107, 20, 7, 87, 17, 103, 167, 56, 67, 3, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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