Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59acb69303f61b9796bde3752d517cf4bc4c79297b47c8293d62031a74d7a703

Tx prefix hash: dd1eee223f7fd2f515b1add1aa9aada60bda6acfe2c43206c58bca14cf93ccc7
Tx public key: dde07035492162d24abdbe966071afe281bf0a7ea4629c5abd8830486e2d0443
Timestamp: 1718441196 Timestamp [UCT]: 2024-06-15 08:46:36 Age [y:d:h:m:s]: 00:293:07:36:36
Block: 1044647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209594 RingCT/type: yes/0
Extra: 01dde07035492162d24abdbe966071afe281bf0a7ea4629c5abd8830486e2d0443021100000002cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b080cd7744d2e720f6f7d62bf01d36c4bf0268563ab48bd0a09e7a673623c7a 0.600000000000 1514010 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": 1044657, "vin": [ { "gen": { "height": 1044647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b080cd7744d2e720f6f7d62bf01d36c4bf0268563ab48bd0a09e7a673623c7a" } } ], "extra": [ 1, 221, 224, 112, 53, 73, 33, 98, 210, 74, 189, 190, 150, 96, 113, 175, 226, 129, 191, 10, 126, 164, 98, 156, 90, 189, 136, 48, 72, 110, 45, 4, 67, 2, 17, 0, 0, 0, 2, 205, 99, 251, 27, 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