Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f910078bd9e5420cd6572cfa70430be0a14e006f654cec440541f79d0d45ae6

Tx prefix hash: fca246ca8f12a72d8ee7916ecc86b52ad21bf7e4e2f2e2ef6a026df1bde57059
Tx public key: 6a4be78543eab1c1525e050ebcb7db63f885c58e8b216dbb380d9093a08dea5c
Timestamp: 1755049619 Timestamp [UCT]: 2025-08-13 01:46:59 Age [y:d:h:m:s]: 00:067:17:43:36
Block: 1345757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47799 RingCT/type: yes/0
Extra: 016a4be78543eab1c1525e050ebcb7db63f885c58e8b216dbb380d9093a08dea5c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aaf75cf12737053af86295ed93bcbbd574eaa622116b927940f2fb4c44dc8dd 0.600000000000 1833652 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": 1345767, "vin": [ { "gen": { "height": 1345757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aaf75cf12737053af86295ed93bcbbd574eaa622116b927940f2fb4c44dc8dd" } } ], "extra": [ 1, 106, 75, 231, 133, 67, 234, 177, 193, 82, 94, 5, 14, 188, 183, 219, 99, 248, 133, 197, 142, 139, 33, 109, 187, 56, 13, 144, 147, 160, 141, 234, 92, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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