Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358662f560184335ecc80fe2ec3bcc91eeb6a135a8b4ef095d8dc058901e3357

Tx prefix hash: 633b9b2cb5a104f3afe31daee428da6b9188e1c363d5d5a362e11576d2cadedc
Tx public key: 4e1af1915a0b30b6a2eb194a4a0b17a8d456eb57a3d6ee3a6900cb3758e81cd2
Timestamp: 1666970547 Timestamp [UCT]: 2022-10-28 15:22:27 Age [y:d:h:m:s]: 02:031:23:43:53
Block: 618904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544730 RingCT/type: yes/0
Extra: 014e1af1915a0b30b6a2eb194a4a0b17a8d456eb57a3d6ee3a6900cb3758e81cd20211000000017e406890000000000000000000

1 output(s) for total of 5.461527953000 dcy

stealth address amount amount idx
00: b133c71d238f2fd0a30c9873aa929db4190a9280d5fe34c72f89759bc9aa5eef 5.461527953000 1056673 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": 618914, "vin": [ { "gen": { "height": 618904 } } ], "vout": [ { "amount": 5461527953, "target": { "key": "b133c71d238f2fd0a30c9873aa929db4190a9280d5fe34c72f89759bc9aa5eef" } } ], "extra": [ 1, 78, 26, 241, 145, 90, 11, 48, 182, 162, 235, 25, 74, 74, 11, 23, 168, 212, 86, 235, 87, 163, 214, 238, 58, 105, 0, 203, 55, 88, 232, 28, 210, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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