Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4531cd1af1fba1bdc8a5c7d00458257f77ffad109889033e5a54dfc3b81e414

Tx prefix hash: f6236f8bcee39e8469f9c88c656d90a6c0bc3761ab8bab7fbeca04c69b6d2d42
Tx public key: 45eb9ce31b63de72512ae3c27010b5daa69d12a4244972b5efe82ceb5eaa19c4
Timestamp: 1733409086 Timestamp [UCT]: 2024-12-05 14:31:26 Age [y:d:h:m:s]: 00:120:02:55:27
Block: 1168626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85641 RingCT/type: yes/0
Extra: 0145eb9ce31b63de72512ae3c27010b5daa69d12a4244972b5efe82ceb5eaa19c4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c29c3001f39367216fd56577423d087fd81331b709e56d754d0b8af76bd77fa0 0.600000000000 1654337 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": 1168636, "vin": [ { "gen": { "height": 1168626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c29c3001f39367216fd56577423d087fd81331b709e56d754d0b8af76bd77fa0" } } ], "extra": [ 1, 69, 235, 156, 227, 27, 99, 222, 114, 81, 42, 227, 194, 112, 16, 181, 218, 166, 157, 18, 164, 36, 73, 114, 181, 239, 232, 44, 235, 94, 170, 25, 196, 2, 17, 0, 0, 0, 3, 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