Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf2eff9ba20f0e0be7567cb7e74985f5bab64a58f7cbb1cdd51c401a974acd6

Tx prefix hash: 418c061f3c20d4251a13ad795cb795126233dff0e177881f4a44538523f749d8
Tx public key: 4a07e7b5bf0e621ad6eeeee11bf4c4a6a9fde76729e6ba1e85a56cfd22da2613
Timestamp: 1707667206 Timestamp [UCT]: 2024-02-11 16:00:06 Age [y:d:h:m:s]: 01:015:15:51:42
Block: 955301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272210 RingCT/type: yes/0
Extra: 014a07e7b5bf0e621ad6eeeee11bf4c4a6a9fde76729e6ba1e85a56cfd22da26130211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e31589ea023da011e75a76c08029b63e6718e3ee6b6df5e491eeee7f969d766 0.600000000000 1414587 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": 955311, "vin": [ { "gen": { "height": 955301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e31589ea023da011e75a76c08029b63e6718e3ee6b6df5e491eeee7f969d766" } } ], "extra": [ 1, 74, 7, 231, 181, 191, 14, 98, 26, 214, 238, 238, 225, 27, 244, 196, 166, 169, 253, 231, 103, 41, 230, 186, 30, 133, 165, 108, 253, 34, 218, 38, 19, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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