Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e448359682e23e8139b91196672fb4e292dc19ba56979343005bfc52f084b81b

Tx prefix hash: 1d0ebf7c522f6a10c322bc05ac220f178f7a721d0ef3f5858ba618504239fe48
Tx public key: 6c2346df69dfc27f046d2e9164957ef910a8b47b2639b7f47743105ded64fc2b
Timestamp: 1729245138 Timestamp [UCT]: 2024-10-18 09:52:18 Age [y:d:h:m:s]: 00:232:22:26:20
Block: 1134208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166297 RingCT/type: yes/0
Extra: 016c2346df69dfc27f046d2e9164957ef910a8b47b2639b7f47743105ded64fc2b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bf7d87e2fdc26ccfa8cbec9a383e69df01a0d9b7494a2b4e2f96290d17d0f23 0.600000000000 1617475 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": 1134218, "vin": [ { "gen": { "height": 1134208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bf7d87e2fdc26ccfa8cbec9a383e69df01a0d9b7494a2b4e2f96290d17d0f23" } } ], "extra": [ 1, 108, 35, 70, 223, 105, 223, 194, 127, 4, 109, 46, 145, 100, 149, 126, 249, 16, 168, 180, 123, 38, 57, 183, 244, 119, 67, 16, 93, 237, 100, 252, 43, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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