Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6aed3c882ee3174874a2ad6cf21543d872869b271b193b6bb64a15c56e4ef49

Tx prefix hash: 6b99c2830dd86a96c93617676e525f16d4dc78467a11b828319d2843d233cb4b
Tx public key: 616549b3858fe8cc05ab0f284944826aa885d5efc305b9a2d9d13cc7b3640aab
Timestamp: 1646678156 Timestamp [UCT]: 2022-03-07 18:35:56 Age [y:d:h:m:s]: 03:238:08:30:51
Block: 453442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 948211 RingCT/type: yes/0
Extra: 01616549b3858fe8cc05ab0f284944826aa885d5efc305b9a2d9d13cc7b3640aab0211000000034a0f5013000000000000000000

1 output(s) for total of 19.300061593000 dcy

stealth address amount amount idx
00: 5f6f635a29b73f81bbb036e3688accc364aaedde66c0d1bd6db618cd65ed4d0e 19.300061593000 868911 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": 453452, "vin": [ { "gen": { "height": 453442 } } ], "vout": [ { "amount": 19300061593, "target": { "key": "5f6f635a29b73f81bbb036e3688accc364aaedde66c0d1bd6db618cd65ed4d0e" } } ], "extra": [ 1, 97, 101, 73, 179, 133, 143, 232, 204, 5, 171, 15, 40, 73, 68, 130, 106, 168, 133, 213, 239, 195, 5, 185, 162, 217, 209, 60, 199, 179, 100, 10, 171, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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