Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b174e0d78c716815ad00661ad46547a5b1aa720167b47615bca776925d873e7a

Tx prefix hash: 11ea5ef59ce2057564538fe9e527a7627c8fe3cc6323b25541a4bf2e5974d25e
Tx public key: c1578cb0f37ba3c17f6a19745805f0020ad6b55bd42a25ba55615cc5a3dc8df6
Timestamp: 1722635980 Timestamp [UCT]: 2024-08-02 21:59:40 Age [y:d:h:m:s]: 00:300:17:13:50
Block: 1079405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214874 RingCT/type: yes/0
Extra: 01c1578cb0f37ba3c17f6a19745805f0020ad6b55bd42a25ba55615cc5a3dc8df602110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bf4b4cd2dd92e51374df2c0d4d255ed5c64a14eb59832112e643ee3d5c8c3db 0.600000000000 1552348 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": 1079415, "vin": [ { "gen": { "height": 1079405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bf4b4cd2dd92e51374df2c0d4d255ed5c64a14eb59832112e643ee3d5c8c3db" } } ], "extra": [ 1, 193, 87, 140, 176, 243, 123, 163, 193, 127, 106, 25, 116, 88, 5, 240, 2, 10, 214, 181, 91, 212, 42, 37, 186, 85, 97, 92, 197, 163, 220, 141, 246, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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