Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29618a87e3c00443dc5d257a0c2e59d1020b5f8b8c0a91b932ca848c8c9af51

Tx prefix hash: 5f1d94c4c82216fa08ba17da5d8294bd21408631bd338eab9433f96ee47745c8
Tx public key: 89071fbe534f39efb17b6f456434297b16dc49a7befa3f422fd0257745af8918
Timestamp: 1673628238 Timestamp [UCT]: 2023-01-13 16:43:58 Age [y:d:h:m:s]: 02:044:18:11:14
Block: 673966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553634 RingCT/type: yes/0
Extra: 0189071fbe534f39efb17b6f456434297b16dc49a7befa3f422fd0257745af891802110000000583600029000000000000000000

1 output(s) for total of 3.588151873000 dcy

stealth address amount amount idx
00: badaf72c3a8698db00a8aeb4fcf7a1ad675fbb9005d5fdbec6a4a04e2badc9a6 3.588151873000 1115599 of 0

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": 673976, "vin": [ { "gen": { "height": 673966 } } ], "vout": [ { "amount": 3588151873, "target": { "key": "badaf72c3a8698db00a8aeb4fcf7a1ad675fbb9005d5fdbec6a4a04e2badc9a6" } } ], "extra": [ 1, 137, 7, 31, 190, 83, 79, 57, 239, 177, 123, 111, 69, 100, 52, 41, 123, 22, 220, 73, 167, 190, 250, 63, 66, 47, 208, 37, 119, 69, 175, 137, 24, 2, 17, 0, 0, 0, 5, 131, 96, 0, 41, 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