Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e73c1131f5e200f11a76716bbfef1e8c83897afb0a4cbb33944827479a55a3e

Tx prefix hash: a1e6c5892430b2830977d0308556d4a73ed765f20f6e6901585f505406fc9f4f
Tx public key: 29f48b7b1c50e90f75b61b1d174d6ae2a929a840f42c11ed0e6a0ce101c5f3d0
Timestamp: 1711061701 Timestamp [UCT]: 2024-03-21 22:55:01 Age [y:d:h:m:s]: 01:053:16:16:33
Block: 983472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299359 RingCT/type: yes/0
Extra: 0129f48b7b1c50e90f75b61b1d174d6ae2a929a840f42c11ed0e6a0ce101c5f3d002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9529e57d4f53c7e361fc8472fbdc9f7ba20c1749ea9c763ee458fd8f332ffe8c 0.600000000000 1443603 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": 983482, "vin": [ { "gen": { "height": 983472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9529e57d4f53c7e361fc8472fbdc9f7ba20c1749ea9c763ee458fd8f332ffe8c" } } ], "extra": [ 1, 41, 244, 139, 123, 28, 80, 233, 15, 117, 182, 27, 29, 23, 77, 106, 226, 169, 41, 168, 64, 244, 44, 17, 237, 14, 106, 12, 225, 1, 197, 243, 208, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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