Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb04ecb6b47e201f410db90a4b3b1e0a8e279a9aa42b385e952cc69bf7a92e0

Tx prefix hash: 7ad7fe5aa41c4ca7fc75fe3432d12882b5aab8bc8f8e18a0073b2f8420f3d66f
Tx public key: b615b22f5b99ae4affdbd3eab0fce224ba5c7a6e31baeddaad99e9dedd4bc1a6
Timestamp: 1746469480 Timestamp [UCT]: 2025-05-05 18:24:40 Age [y:d:h:m:s]: 00:009:14:52:56
Block: 1276474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6884 RingCT/type: yes/0
Extra: 01b615b22f5b99ae4affdbd3eab0fce224ba5c7a6e31baeddaad99e9dedd4bc1a60211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c08994234f8d93b66da3d7a6893aea89ff66682dfa3616abdbf17c582fce42b 0.600000000000 1763819 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": 1276484, "vin": [ { "gen": { "height": 1276474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c08994234f8d93b66da3d7a6893aea89ff66682dfa3616abdbf17c582fce42b" } } ], "extra": [ 1, 182, 21, 178, 47, 91, 153, 174, 74, 255, 219, 211, 234, 176, 252, 226, 36, 186, 92, 122, 110, 49, 186, 237, 218, 173, 153, 233, 222, 221, 75, 193, 166, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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