Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3619195d5cd4dcefafb948ddd61eb2ffbefc7384d0831b9de06e40ecf502c266

Tx prefix hash: 37f7d4aef502a1d3fe6662737abfe1707152793670f64139a0c295f93dbabc0c
Tx public key: a8ee7a4c248a87d8bdf1a799cd7d81a85a3f7a755005dd21c5f5e7bd8a5060ca
Timestamp: 1737257835 Timestamp [UCT]: 2025-01-19 03:37:15 Age [y:d:h:m:s]: 00:150:20:18:29
Block: 1200446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107531 RingCT/type: yes/0
Extra: 01a8ee7a4c248a87d8bdf1a799cd7d81a85a3f7a755005dd21c5f5e7bd8a5060ca021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c25d43db8467ebab708086934df08131fbefe0819dff4a66dc1c2ff63063de03 0.600000000000 1687089 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": 1200456, "vin": [ { "gen": { "height": 1200446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c25d43db8467ebab708086934df08131fbefe0819dff4a66dc1c2ff63063de03" } } ], "extra": [ 1, 168, 238, 122, 76, 36, 138, 135, 216, 189, 241, 167, 153, 205, 125, 129, 168, 90, 63, 122, 117, 80, 5, 221, 33, 197, 245, 231, 189, 138, 80, 96, 202, 2, 17, 0, 0, 0, 6, 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