Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ca9eb04c0ef38decab11cba66b4e2d5ade4511386925db21514bd53a045480

Tx prefix hash: cf1674e14739c2457b5092ecd2b26e1266e6c246b5ea4ee42da80a8d593281c9
Tx public key: 1dfd7ac62caf20a1f4db8687b8f156147f60bcfc6bfcfda3c5ae1d77be681139
Timestamp: 1731660742 Timestamp [UCT]: 2024-11-15 08:52:22 Age [y:d:h:m:s]: 00:139:00:09:58
Block: 1154135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99162 RingCT/type: yes/0
Extra: 011dfd7ac62caf20a1f4db8687b8f156147f60bcfc6bfcfda3c5ae1d77be6811390211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c30534d008ec8f00be6bf8d78a897e830eca9b6ca1ec2a6c6a216164a52ec9 0.600000000000 1639746 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": 1154145, "vin": [ { "gen": { "height": 1154135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c30534d008ec8f00be6bf8d78a897e830eca9b6ca1ec2a6c6a216164a52ec9" } } ], "extra": [ 1, 29, 253, 122, 198, 44, 175, 32, 161, 244, 219, 134, 135, 184, 241, 86, 20, 127, 96, 188, 252, 107, 252, 253, 163, 197, 174, 29, 119, 190, 104, 17, 57, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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