Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 281a3673271d2f5014a64d4e3e223caff000c40a8dc0fe5fa636b9430fe4007b

Tx prefix hash: e52cad4c5544625f4c6099c02a90be798af34b6f505639260d522a4f420b5ef0
Tx public key: 38292edd98dc959f641c7a47b2ecc1d2a85a737f92068bf210dbfc2b39075cf4
Timestamp: 1737809181 Timestamp [UCT]: 2025-01-25 12:46:21 Age [y:d:h:m:s]: 00:336:11:32:14
Block: 1205009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238078 RingCT/type: yes/0
Extra: 0138292edd98dc959f641c7a47b2ecc1d2a85a737f92068bf210dbfc2b39075cf4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f6adf8126fe218d5c0a64e516e9b06cbefa3600b64db5873131e5be4b1f1e5 0.600000000000 1691704 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": 1205019, "vin": [ { "gen": { "height": 1205009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f6adf8126fe218d5c0a64e516e9b06cbefa3600b64db5873131e5be4b1f1e5" } } ], "extra": [ 1, 56, 41, 46, 221, 152, 220, 149, 159, 100, 28, 122, 71, 178, 236, 193, 210, 168, 90, 115, 127, 146, 6, 139, 242, 16, 219, 252, 43, 57, 7, 92, 244, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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