Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90cbfb8a6652888d6d307826064e092f1b17fda7caab12d5a6f11c580a3ab68a

Tx prefix hash: 418eaef654ec05f729374b60252214a76086ca9b962e0923fd0a8227e9796b98
Tx public key: 9b19e99124d4ee1588b2de7978df8535df868fbb188c68927060f67c8c31054a
Timestamp: 1742621552 Timestamp [UCT]: 2025-03-22 05:32:32 Age [y:d:h:m:s]: 00:313:11:32:28
Block: 1244619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221700 RingCT/type: yes/0
Extra: 019b19e99124d4ee1588b2de7978df8535df868fbb188c68927060f67c8c31054a021100000004af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b124b5c73b423eb8a710e820f44c8e9fb9057da96e7e2036c63b243a8e9e666 0.600000000000 1731610 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": 1244629, "vin": [ { "gen": { "height": 1244619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b124b5c73b423eb8a710e820f44c8e9fb9057da96e7e2036c63b243a8e9e666" } } ], "extra": [ 1, 155, 25, 233, 145, 36, 212, 238, 21, 136, 178, 222, 121, 120, 223, 133, 53, 223, 134, 143, 187, 24, 140, 104, 146, 112, 96, 246, 124, 140, 49, 5, 74, 2, 17, 0, 0, 0, 4, 175, 132, 86, 73, 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