Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ac184d26b4e4021ad0a5734543732fa88421bfa6614fbdd308a400c7ba9fa2

Tx prefix hash: 92fe994b4a72e378bcd2f824129130d5b260e7b201b294354575bfe3b61a2fc4
Tx public key: 876bd9d498fb796a496038475da6f4ce60c25a06cab8f8139a42f6cbcd899429
Timestamp: 1752125922 Timestamp [UCT]: 2025-07-10 05:38:42 Age [y:d:h:m:s]: 00:166:20:44:16
Block: 1322431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117838 RingCT/type: yes/0
Extra: 01876bd9d498fb796a496038475da6f4ce60c25a06cab8f8139a42f6cbcd89942902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29d01405f4e4373b0cae7b28ddd2ff0c6f388f215bd2ec0fb56afbc1808c7a7 0.600000000000 1810160 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": 1322441, "vin": [ { "gen": { "height": 1322431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29d01405f4e4373b0cae7b28ddd2ff0c6f388f215bd2ec0fb56afbc1808c7a7" } } ], "extra": [ 1, 135, 107, 217, 212, 152, 251, 121, 106, 73, 96, 56, 71, 93, 166, 244, 206, 96, 194, 90, 6, 202, 184, 248, 19, 154, 66, 246, 203, 205, 137, 148, 41, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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