Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe18014e4130e49f40d9b14c213c88a298f10a39b1cda35af59bff4a5d73fe6

Tx prefix hash: c47c7b85a884985872fc07f204e94b842b42594a65084b2becbda2007a23351c
Tx public key: 062ce21286b6d8d2d4134eea983163c5af77aa4320d0ad8148e2bb19e126dca2
Timestamp: 1717880605 Timestamp [UCT]: 2024-06-08 21:03:25 Age [y:d:h:m:s]: 00:339:23:52:17
Block: 1039986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243012 RingCT/type: yes/0
Extra: 01062ce21286b6d8d2d4134eea983163c5af77aa4320d0ad8148e2bb19e126dca2021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f479d0cfb9c57b909b249c3607594be192f510b8e5c0eef13f19fb33c87366e1 0.600000000000 1508641 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": 1039996, "vin": [ { "gen": { "height": 1039986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f479d0cfb9c57b909b249c3607594be192f510b8e5c0eef13f19fb33c87366e1" } } ], "extra": [ 1, 6, 44, 226, 18, 134, 182, 216, 210, 212, 19, 78, 234, 152, 49, 99, 197, 175, 119, 170, 67, 32, 208, 173, 129, 72, 226, 187, 25, 225, 38, 220, 162, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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