Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff19a6f6e5bfe71dfd1cf03f3bdf79052bb8aef02cb9af799d44837514202db

Tx prefix hash: 255b8297f045d4f6cda08bb255dd0166e5d192e5a264c116a79506f44a24c223
Tx public key: 7551fd60e6f7db2bd62df4d2d93508d00dfd4b2df8efad093d9eb4948cabb3ba
Timestamp: 1721753278 Timestamp [UCT]: 2024-07-23 16:47:58 Age [y:d:h:m:s]: 00:252:03:45:51
Block: 1072083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180125 RingCT/type: yes/0
Extra: 017551fd60e6f7db2bd62df4d2d93508d00dfd4b2df8efad093d9eb4948cabb3ba02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da6e851fe8700a9f7d5b0a9fa25ec2a86d868cdc3c09db2e0fdfdb325107ca8b 0.600000000000 1544530 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": 1072093, "vin": [ { "gen": { "height": 1072083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da6e851fe8700a9f7d5b0a9fa25ec2a86d868cdc3c09db2e0fdfdb325107ca8b" } } ], "extra": [ 1, 117, 81, 253, 96, 230, 247, 219, 43, 214, 45, 244, 210, 217, 53, 8, 208, 13, 253, 75, 45, 248, 239, 173, 9, 61, 158, 180, 148, 140, 171, 179, 186, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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