Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf915f9dea04fb58b1f3212ece84b9ac999a29c047727e4bc216751f579af93

Tx prefix hash: 83f3db37cc573cfcad6cae014a31b957e75f59096d35b9d409f5efa1ed8635e5
Tx public key: bb863109851d573334f13df186456f2fe8899b19a2a8bd4eaeb7c4a79b27382b
Timestamp: 1710156613 Timestamp [UCT]: 2024-03-11 11:30:13 Age [y:d:h:m:s]: 01:036:18:43:20
Block: 975962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287273 RingCT/type: yes/0
Extra: 01bb863109851d573334f13df186456f2fe8899b19a2a8bd4eaeb7c4a79b27382b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2a4e7754153b9151a1976fd62898ab352cfc305ac8b1a83e2b73b680551b17c 0.600000000000 1435941 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": 975972, "vin": [ { "gen": { "height": 975962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2a4e7754153b9151a1976fd62898ab352cfc305ac8b1a83e2b73b680551b17c" } } ], "extra": [ 1, 187, 134, 49, 9, 133, 29, 87, 51, 52, 241, 61, 241, 134, 69, 111, 47, 232, 137, 155, 25, 162, 168, 189, 78, 174, 183, 196, 167, 155, 39, 56, 43, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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