Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51874aeb11209e6b7a3e0a0d7c7515baf6178039453635be71c93db862eec4e3

Tx prefix hash: b63f076cd28f0fd6770c0345bd626764da15bd16b588e3ca6add90677f0f78d0
Tx public key: 0fe751455b33db249ff1bf52e5a0fbe0d0282e946e873cc5d4593200f7f170e8
Timestamp: 1740303713 Timestamp [UCT]: 2025-02-23 09:41:53 Age [y:d:h:m:s]: 00:226:22:04:26
Block: 1225417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159886 RingCT/type: yes/0
Extra: 010fe751455b33db249ff1bf52e5a0fbe0d0282e946e873cc5d4593200f7f170e8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c56e779942d4d2bdc1b0a2325d27195ccede531e0ae2221d1a1f14cd73a31a41 0.600000000000 1712282 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": 1225427, "vin": [ { "gen": { "height": 1225417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c56e779942d4d2bdc1b0a2325d27195ccede531e0ae2221d1a1f14cd73a31a41" } } ], "extra": [ 1, 15, 231, 81, 69, 91, 51, 219, 36, 159, 241, 191, 82, 229, 160, 251, 224, 208, 40, 46, 148, 110, 135, 60, 197, 212, 89, 50, 0, 247, 241, 112, 232, 2, 17, 0, 0, 0, 4, 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