Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c6979a8e3676c74fd16fc5cb08fc21df2caf23b7f89eef030dcbb23071d774

Tx prefix hash: 332265430cb30346021fa6070f0f089ffe7d394eea64b320fafeb059b860c080
Tx public key: d47ba7baa8fd5a1f77494bc5964dbc9139c831cd8e419cb5129120088ea8423f
Timestamp: 1706162402 Timestamp [UCT]: 2024-01-25 06:00:02 Age [y:d:h:m:s]: 01:300:21:09:51
Block: 942802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473860 RingCT/type: yes/0
Extra: 01d47ba7baa8fd5a1f77494bc5964dbc9139c831cd8e419cb5129120088ea8423f02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e88a39032ba2872b43182bf0889994ac2e159e7aa2e4c1f583df6ad5f10b86a9 0.600000000000 1400980 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": 942812, "vin": [ { "gen": { "height": 942802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e88a39032ba2872b43182bf0889994ac2e159e7aa2e4c1f583df6ad5f10b86a9" } } ], "extra": [ 1, 212, 123, 167, 186, 168, 253, 90, 31, 119, 73, 75, 197, 150, 77, 188, 145, 57, 200, 49, 205, 142, 65, 156, 181, 18, 145, 32, 8, 142, 168, 66, 63, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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