Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d00f6c1e330f49347981ed6587c219bded8988a30c0dad748e859d5644cb16

Tx prefix hash: 7f338cc7a062d67544c5825d2530f6e37e1289c020a8eb7a411e1e447422151a
Tx public key: 313d4a725b93d7656ddd8ffdaec59e15734184c64b3d310c308e7521e8533179
Timestamp: 1708950908 Timestamp [UCT]: 2024-02-26 12:35:08 Age [y:d:h:m:s]: 00:362:18:36:27
Block: 965958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259375 RingCT/type: yes/0
Extra: 01313d4a725b93d7656ddd8ffdaec59e15734184c64b3d310c308e7521e85331790211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a0ab8b90de6f3c0593ac005dd92e21f97fc6a7c1aeb48e03e2c23802f1055b 0.600000000000 1425713 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": 965968, "vin": [ { "gen": { "height": 965958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a0ab8b90de6f3c0593ac005dd92e21f97fc6a7c1aeb48e03e2c23802f1055b" } } ], "extra": [ 1, 49, 61, 74, 114, 91, 147, 215, 101, 109, 221, 143, 253, 174, 197, 158, 21, 115, 65, 132, 198, 75, 61, 49, 12, 48, 142, 117, 33, 232, 83, 49, 121, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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