Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b07505f1d4db708c5f2604c67d34f3b2e610788e5227cfe4e949dab3173ca44

Tx prefix hash: 6c05fb2dad057e04d1197e21645bffde1947c34b6624cfc2fb29ddcf8a9fcbb3
Tx public key: 0b0fa9c030ed16610d01a524610d0c1b561cd167dac9864955aca1ba57ef9d23
Timestamp: 1695911726 Timestamp [UCT]: 2023-09-28 14:35:26 Age [y:d:h:m:s]: 01:113:11:54:23
Block: 858059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342352 RingCT/type: yes/0
Extra: 010b0fa9c030ed16610d01a524610d0c1b561cd167dac9864955aca1ba57ef9d2302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.880834630000 dcy

stealth address amount amount idx
00: 3c5605d7c1239b0c0a37386d683c4c3275f5029c2edcd2c694e8f37197be2f6a 0.880834630000 1312217 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": 858069, "vin": [ { "gen": { "height": 858059 } } ], "vout": [ { "amount": 880834630, "target": { "key": "3c5605d7c1239b0c0a37386d683c4c3275f5029c2edcd2c694e8f37197be2f6a" } } ], "extra": [ 1, 11, 15, 169, 192, 48, 237, 22, 97, 13, 1, 165, 36, 97, 13, 12, 27, 86, 28, 209, 103, 218, 201, 134, 73, 85, 172, 161, 186, 87, 239, 157, 35, 2, 17, 0, 0, 0, 6, 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