Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b78a1380e0f9982e8d20bf645e65fd2b5c466e66ea04aacc9ff4f7e5e5b32d46

Tx prefix hash: b1f4f87bab109d15932cd65cf9fc1c566b5eb1e8eed5f02b5d2bb1194b66eb1f
Tx public key: dfe7728a0b79b4d55da20ba256942e0afdbcfc69bfd24d9efba4c5eb87215c6a
Timestamp: 1703130115 Timestamp [UCT]: 2023-12-21 03:41:55 Age [y:d:h:m:s]: 01:315:16:33:05
Block: 917717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484449 RingCT/type: yes/0
Extra: 01dfe7728a0b79b4d55da20ba256942e0afdbcfc69bfd24d9efba4c5eb87215c6a021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 431c0669ca048d9d2b9e63a25b8dfaf5ebd80149feb013fed5ea6fa83d2be37f 0.600000000000 1375299 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": 917727, "vin": [ { "gen": { "height": 917717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "431c0669ca048d9d2b9e63a25b8dfaf5ebd80149feb013fed5ea6fa83d2be37f" } } ], "extra": [ 1, 223, 231, 114, 138, 11, 121, 180, 213, 93, 162, 11, 162, 86, 148, 46, 10, 253, 188, 252, 105, 191, 210, 77, 158, 251, 164, 197, 235, 135, 33, 92, 106, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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