Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435d3d395447da596752ce5165993cec5add6194c99991fdfac44c453e110af0

Tx prefix hash: b2c3f4a30ba193b53870f602644e8bff8b8b0e24b050b9c6f64f0346918ac8e8
Tx public key: 9f909201adf113a465f4b70d254f9f2f0d95c2f35453c4a3b6f26160d44ee205
Timestamp: 1698437812 Timestamp [UCT]: 2023-10-27 20:16:52 Age [y:d:h:m:s]: 01:087:08:44:38
Block: 879009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323615 RingCT/type: yes/0
Extra: 019f909201adf113a465f4b70d254f9f2f0d95c2f35453c4a3b6f26160d44ee20502110000000279bda3be000000000000000000

1 output(s) for total of 0.750720548000 dcy

stealth address amount amount idx
00: ac38b5a56fb29b3fd8c7409cf45bed14a0c82d79302dbbfc70a2c8f9d1c9755c 0.750720548000 1334505 of 0

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": 879019, "vin": [ { "gen": { "height": 879009 } } ], "vout": [ { "amount": 750720548, "target": { "key": "ac38b5a56fb29b3fd8c7409cf45bed14a0c82d79302dbbfc70a2c8f9d1c9755c" } } ], "extra": [ 1, 159, 144, 146, 1, 173, 241, 19, 164, 101, 244, 183, 13, 37, 79, 159, 47, 13, 149, 194, 243, 84, 83, 196, 163, 182, 242, 97, 96, 212, 78, 226, 5, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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