Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00db3b42824725fbc4d80a03150b45c4c43b8d71e7de669369e994b02edfd18a

Tx prefix hash: 887a23025573d511675a3b11739286c17a75fb6d4e73fcd273b251ac5a64a59c
Tx public key: fb341527045cca29a83042fff2f0e23bef1d4862a08edc1b0b6b0d8d2605c641
Timestamp: 1727893757 Timestamp [UCT]: 2024-10-02 18:29:17 Age [y:d:h:m:s]: 01:038:11:38:53
Block: 1123011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285880 RingCT/type: yes/0
Extra: 01fb341527045cca29a83042fff2f0e23bef1d4862a08edc1b0b6b0d8d2605c64102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f55b1f72645d560046e71b31e9a026628319593376f3c721edc139f2619575 0.600000000000 1605544 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": 1123021, "vin": [ { "gen": { "height": 1123011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f55b1f72645d560046e71b31e9a026628319593376f3c721edc139f2619575" } } ], "extra": [ 1, 251, 52, 21, 39, 4, 92, 202, 41, 168, 48, 66, 255, 242, 240, 226, 59, 239, 29, 72, 98, 160, 142, 220, 27, 11, 107, 13, 141, 38, 5, 198, 65, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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