Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fb22d26c1593dc0dac328aee58b76d08ba8aa401b58fdf475338c3bfe69aabb

Tx prefix hash: 13efd50fce2493e4db48eedc434bbe4c5d910787dfa3259820c6ed92b38bebad
Tx public key: edc5a4129ae7b372f89cb590c3c369cdf69146ca5f1233efaf8074a6f7f0a732
Timestamp: 1734803812 Timestamp [UCT]: 2024-12-21 17:56:52 Age [y:d:h:m:s]: 00:101:09:17:20
Block: 1180196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72210 RingCT/type: yes/0
Extra: 01edc5a4129ae7b372f89cb590c3c369cdf69146ca5f1233efaf8074a6f7f0a732021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1ab39cd61cec55f57e382d1b4fac13872a0b0164f1fc36d4c2d6f696e02700 0.600000000000 1666605 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": 1180206, "vin": [ { "gen": { "height": 1180196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1ab39cd61cec55f57e382d1b4fac13872a0b0164f1fc36d4c2d6f696e02700" } } ], "extra": [ 1, 237, 197, 164, 18, 154, 231, 179, 114, 248, 156, 181, 144, 195, 195, 105, 205, 246, 145, 70, 202, 95, 18, 51, 239, 175, 128, 116, 166, 247, 240, 167, 50, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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