Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808d3520af037106e0048fccbc50d1dfc473872e5fecb2ef91b16a66183b9cb6

Tx prefix hash: cd2dd54fb81ec68721c8d50ef69ec4ddce6f835efe3a04091eb89c4801ec38ae
Tx public key: 3ac0a1e473ce8db2a4f9a5692e4d263dbd13e2960b3ab044d2a60b35d2756982
Timestamp: 1745612223 Timestamp [UCT]: 2025-04-25 20:17:03 Age [y:d:h:m:s]: 00:209:15:45:09
Block: 1269382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147552 RingCT/type: yes/0
Extra: 013ac0a1e473ce8db2a4f9a5692e4d263dbd13e2960b3ab044d2a60b35d27569820211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 269a55a52bff897cc2d1e5d47fe195c532781edf7d4fb55826c1893f39a02154 0.600000000000 1756617 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": 1269392, "vin": [ { "gen": { "height": 1269382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "269a55a52bff897cc2d1e5d47fe195c532781edf7d4fb55826c1893f39a02154" } } ], "extra": [ 1, 58, 192, 161, 228, 115, 206, 141, 178, 164, 249, 165, 105, 46, 77, 38, 61, 189, 19, 226, 150, 11, 58, 176, 68, 210, 166, 11, 53, 210, 117, 105, 130, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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