Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ce0fbbb5a4b39ac0e474f30050cab76ac9015ae9c455613ed25186ed7489129

Tx prefix hash: 9eec0a9852f252ca751be8d771073c45e692237de1c028e936df2a16f34022d6
Tx public key: 718d759c412f8d53bdf14f164ecf578743791dfa243b914a7183c01f00198d4c
Timestamp: 1702860140 Timestamp [UCT]: 2023-12-18 00:42:20 Age [y:d:h:m:s]: 01:073:12:35:38
Block: 915458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313643 RingCT/type: yes/0
Extra: 01718d759c412f8d53bdf14f164ecf578743791dfa243b914a7183c01f00198d4c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 173100bbab8b24ea2b03af78398e6bb751fe2b1a96248bab0dd48d7bc4e5d327 0.600000000000 1372854 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": 915468, "vin": [ { "gen": { "height": 915458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "173100bbab8b24ea2b03af78398e6bb751fe2b1a96248bab0dd48d7bc4e5d327" } } ], "extra": [ 1, 113, 141, 117, 156, 65, 47, 141, 83, 189, 241, 79, 22, 78, 207, 87, 135, 67, 121, 29, 250, 36, 59, 145, 74, 113, 131, 192, 31, 0, 25, 141, 76, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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