Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aae8ea0c1a0ab4332152dc69be69d98461d14155edde8d055293eb17d0fe5fb

Tx prefix hash: 1f12f9ac5a7af18e62c69f91c29907562aa946de353985cb5eae372b677bcb6f
Tx public key: 60f968dc969441d7f03fc484720c6cf9255d4a030d28f03df8fccc322f3730d6
Timestamp: 1745809003 Timestamp [UCT]: 2025-04-28 02:56:43 Age [y:d:h:m:s]: 00:009:20:06:38
Block: 1271008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7039 RingCT/type: yes/0
Extra: 0160f968dc969441d7f03fc484720c6cf9255d4a030d28f03df8fccc322f3730d602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e43fa3d74cdb4012d0afa814a65c2a3f436ed43f56e9908dd514ca192e3b4ead 0.600000000000 1758255 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": 1271018, "vin": [ { "gen": { "height": 1271008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e43fa3d74cdb4012d0afa814a65c2a3f436ed43f56e9908dd514ca192e3b4ead" } } ], "extra": [ 1, 96, 249, 104, 220, 150, 148, 65, 215, 240, 63, 196, 132, 114, 12, 108, 249, 37, 93, 74, 3, 13, 40, 240, 61, 248, 252, 204, 50, 47, 55, 48, 214, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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