Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d558ec56a85f457d2c19ca7aa1e920989d1eefc9dfee999dd2ba08dde07f351f

Tx prefix hash: 402f2d27f2eee92baf16bf748ae7aa821b4b1309c9b2b56297118ecbfb8a4a31
Tx public key: 78ec54fec1cf13da90d1a510740d6a03b3321f349869fc62d6d7b888c1e776a8
Timestamp: 1765065690 Timestamp [UCT]: 2025-12-07 00:01:30 Age [y:d:h:m:s]: 00:044:13:38:30
Block: 1428038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31770 RingCT/type: yes/0
Extra: 0178ec54fec1cf13da90d1a510740d6a03b3321f349869fc62d6d7b888c1e776a8021100000014d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21544b0edc499eb1c3485235041b63ca0c30a4873a251b7ff53f6e31722bc17a 0.600000000000 1916747 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": 1428048, "vin": [ { "gen": { "height": 1428038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21544b0edc499eb1c3485235041b63ca0c30a4873a251b7ff53f6e31722bc17a" } } ], "extra": [ 1, 120, 236, 84, 254, 193, 207, 19, 218, 144, 209, 165, 16, 116, 13, 106, 3, 179, 50, 31, 52, 152, 105, 252, 98, 214, 215, 184, 136, 193, 231, 118, 168, 2, 17, 0, 0, 0, 20, 214, 225, 157, 124, 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