Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7c4abea625e6d766897a58cbdbf0dde3357e4a5db14e74af1ac245c688a39a

Tx prefix hash: 9b397bba3afa829130d21879e19f83261c41c371c38eaa113a5b1ba69388d553
Tx public key: 439f8ecaa8cf54db5b78ad825ed192a835216f3b0e342bf133d1df1a69aae3ab
Timestamp: 1730111228 Timestamp [UCT]: 2024-10-28 10:27:08 Age [y:d:h:m:s]: 00:171:22:03:06
Block: 1141304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122718 RingCT/type: yes/0
Extra: 01439f8ecaa8cf54db5b78ad825ed192a835216f3b0e342bf133d1df1a69aae3ab02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73b2a1eff46b93b6efc09344abb64936b1a2ff5a83e957101181851319e08b43 0.600000000000 1625111 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": 1141314, "vin": [ { "gen": { "height": 1141304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73b2a1eff46b93b6efc09344abb64936b1a2ff5a83e957101181851319e08b43" } } ], "extra": [ 1, 67, 159, 142, 202, 168, 207, 84, 219, 91, 120, 173, 130, 94, 209, 146, 168, 53, 33, 111, 59, 14, 52, 43, 241, 51, 209, 223, 26, 105, 170, 227, 171, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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