Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3656a61079fe43a118294d894a82e81a17f5b995f56069aba29bb1ceec8fd128

Tx prefix hash: 763514c131d3b1d7e36acef1fc234ac2ab4c3142baa54c6d66a25b44e5a95792
Tx public key: 35f04a71cf54f47b2d9975b72aa76a81d06d9144672616711d428fd145f2b358
Timestamp: 1715556639 Timestamp [UCT]: 2024-05-12 23:30:39 Age [y:d:h:m:s]: 00:202:23:13:41
Block: 1020746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145257 RingCT/type: yes/0
Extra: 0135f04a71cf54f47b2d9975b72aa76a81d06d9144672616711d428fd145f2b358021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4851edc002209d5a8dc35f3717774cbae57fc721cba0d5c77a4e4b963b1f5e93 0.600000000000 1484827 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": 1020756, "vin": [ { "gen": { "height": 1020746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4851edc002209d5a8dc35f3717774cbae57fc721cba0d5c77a4e4b963b1f5e93" } } ], "extra": [ 1, 53, 240, 74, 113, 207, 84, 244, 123, 45, 153, 117, 183, 42, 167, 106, 129, 208, 109, 145, 68, 103, 38, 22, 113, 29, 66, 143, 209, 69, 242, 179, 88, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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