Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff62beedff8ee129ff6793c26165f82b003b19327a846a289cc4deb97397601

Tx prefix hash: 8bc48e423819c42c935f7411e9fb8b53a35507c1bc9f78f336a7de10cbcfc583
Tx public key: 486081f3a58a841cb6bb9363af9e0f26e1fc9821787cc58af253d7f2bc7c0fb2
Timestamp: 1736315562 Timestamp [UCT]: 2025-01-08 05:52:42 Age [y:d:h:m:s]: 00:082:16:37:14
Block: 1192677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58882 RingCT/type: yes/0
Extra: 01486081f3a58a841cb6bb9363af9e0f26e1fc9821787cc58af253d7f2bc7c0fb20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07b185972265f3164ec15a5b3717fae5e107e2b0dea1e35866bfe0b1b449d17 0.600000000000 1679232 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": 1192687, "vin": [ { "gen": { "height": 1192677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07b185972265f3164ec15a5b3717fae5e107e2b0dea1e35866bfe0b1b449d17" } } ], "extra": [ 1, 72, 96, 129, 243, 165, 138, 132, 28, 182, 187, 147, 99, 175, 158, 15, 38, 225, 252, 152, 33, 120, 124, 197, 138, 242, 83, 215, 242, 188, 124, 15, 178, 2, 17, 0, 0, 0, 6, 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