Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feee0c3512ca6e8340eebe22b73789942747074430a5cb42629a0a4344824d55

Tx prefix hash: 292e0464410f6521410327f72aab8f56107ed409f9affca2e420a565fee6f009
Tx public key: 1dc4a046dffac0d7bc2edf0739870f33aa0d6f3c1c8bca93605bfa49bd2d6ee4
Timestamp: 1718729042 Timestamp [UCT]: 2024-06-18 16:44:02 Age [y:d:h:m:s]: 01:000:19:39:01
Block: 1047015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261329 RingCT/type: yes/0
Extra: 011dc4a046dffac0d7bc2edf0739870f33aa0d6f3c1c8bca93605bfa49bd2d6ee40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31793b3e961c626ac88715f8af2723936bf9854c6ffe580842a383d5eb0e0bad 0.600000000000 1516834 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": 1047025, "vin": [ { "gen": { "height": 1047015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31793b3e961c626ac88715f8af2723936bf9854c6ffe580842a383d5eb0e0bad" } } ], "extra": [ 1, 29, 196, 160, 70, 223, 250, 192, 215, 188, 46, 223, 7, 57, 135, 15, 51, 170, 13, 111, 60, 28, 139, 202, 147, 96, 91, 250, 73, 189, 45, 110, 228, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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