Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba435a8595fa49371e1d40f701a5a904ddcf777c59b133ad1a20406524223c7

Tx prefix hash: c47b356f2d7c12aa50eaafe77d7e79136d87be66c5563e06cc6ebd8270cf4e86
Tx public key: 105bdf08639fa5c6ac0061521f5916f28b70cdc821f748b2c9ddea0345b786e2
Timestamp: 1700945013 Timestamp [UCT]: 2023-11-25 20:43:33 Age [y:d:h:m:s]: 01:167:20:37:23
Block: 899574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381160 RingCT/type: yes/0
Extra: 01105bdf08639fa5c6ac0061521f5916f28b70cdc821f748b2c9ddea0345b786e202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.641708646000 dcy

stealth address amount amount idx
00: f80a0cc21ccccfb5fe95d432eb6de0cc758991de199dff073ed3b05f3c9bbe1b 0.641708646000 1356033 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": 899584, "vin": [ { "gen": { "height": 899574 } } ], "vout": [ { "amount": 641708646, "target": { "key": "f80a0cc21ccccfb5fe95d432eb6de0cc758991de199dff073ed3b05f3c9bbe1b" } } ], "extra": [ 1, 16, 91, 223, 8, 99, 159, 165, 198, 172, 0, 97, 82, 31, 89, 22, 242, 139, 112, 205, 200, 33, 247, 72, 178, 201, 221, 234, 3, 69, 183, 134, 226, 2, 17, 0, 0, 0, 2, 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